On Wed, Jan 16, 2013 at 1:58 PM, Sasha Levin <sasha.le...@oracle.com> wrote:
>
> I guess that if you agree that it should go in once it had some more
> testing, it can go into linux-next and sit there for the next couple
> of weeks until the next merge window opens.
So linux-next gets compile testing and warns about conflicts. But
almost nobody really runs the end result.
Now, *hopefully* the compile problems and conflicts are the major
issue, but at the same time, I worry about some actual subtle semantic
breakage. I'm not sure how it would happen, but it's a big patch..
> What would be the best way to do that though? see if akpm would take
> it into his tree?
That would help. As would just linux-next. As would just after the
next merge window closes, if you can send it almost immediately *and*
have the "at least the patch has been around for a long time with no
*known* breakage" note. Because at some point, I guess we can't do
much more than that.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
