Messages in this thread | | | Date | Wed, 16 Jan 2013 17:17:42 -0500 | From | Sasha Levin <> | Subject | Re: [PATCH v2] hlist: drop the node parameter from iterators |
| |
On 01/16/2013 05:04 PM, Linus Torvalds wrote: > On Wed, Jan 16, 2013 at 1:58 PM, Sasha Levin <sasha.levin@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.
I do :)
I also know that people run ltp tests on top of those builds, so while it's not as good as actually working with it, it's also not insignificant.
> 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.
Alrighty, right after merge window it is. The -rc4 period is what you told me the last time I sent this patch, so I went with that this time.
I'll resend this patch to Andrew in hopes that he'll be okay with having it in his tree until the next window.
Thanks!
| |