Messages in this thread | | | Date | Sat, 5 Jun 2010 11:36:53 +0300 | Subject | Re: [PATCH 1/4] Support generic I/O requests | From | Pekka Enberg <> |
| |
On Sat, Jun 5, 2010 at 11:28 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote: > Andrew Morton wrote: >>> >>> I thought zram is related to memory management a little bit. >>> >>> What's the criteria? >> >> Yes, and this is something which bothers me a bit about the -staging >> process. Code gets in there largely under the radar of the people who >> work in that area. It gets "matured" for a while and the developer >> thinks it's all ready to go into "mainline" and .... then what? Someone >> needs to yank the code out of -staging and tell the interested >> parties "hey, look at this". And at this stage, they might say "hell >> no", or request large changes and the developer who thought everything >> was all ready to go would be justifiably upset. > > Yeah, that's what I assumed would happen here. When the code in -staging is > "good enough", Nitin would submit squashed patches for inclusion review and > when everyone is happy, we'd merge the code including full history from > -staging. > > Btw, ramzswap and zram have been discussed openly on LKML. I guess Nitin > should have CC'd linux-mm as well for you to see it Andrew?
Sorry for the duplicate mail. I thought I lost this to /dev/null. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |