On Thu, Aug 25, 2011 at 10:23:21PM -0700, Olof Johansson wrote:

Ok. Sounds like there might be some use for a temporary "work in
progress" branch for linux-next for patches that are nearly ready to
go but not quite that needs air time, but not really for anything
beyond that.

Bad idea.

linux-next's policy is that everything in linux-next should be ready
for mainline - not nearly ready.

Linus is threatening at the next merge window to ignore pull requests
from maintainers, and just pull the entire linux-next tree into his at
the beginning.  Anything in linux-next which is "work in progress" will
therefore find its way immediately into mainline in whatever state it's
in.

So, everyone needs to ensure that linux-next only contains code that's
100% ready for merging during the next merge window.  Everything else
should not be in linux-next.