On Sun, 17 Jun 2012, Wanpeng Li wrote: > >acked, and then ask for it to be merged after an -rc1 release to avoid > >lots of conflicts with other people's work. > > You mean trivial maintainer only pull trivial patches for -rc1 release ? > It all depends on how big your patch turns out to be; if it's sufficiently large then it would probably be best to wait for -rc1, rebase your patch to it, carry any acks that you have received, and ask it to be merged for -rc2 to reduce conflicts with other code being pushed during the merge window. Otherwise, just make a big patch and ask Andrew to carry it in the -mm tree but make sure to base it off linux-next as it sits today. You'll want to clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>