On Thu, Mar 28, 2013 at 07:39:01PM +0000, Ben Hutchings wrote: > On Thu, Mar 28, 2013 at 12:04:29PM -0400, Naoya Horiguchi wrote: > [...] > > I guess you mean this patch violates one/both of these rules: > > > > - It must fix a problem that causes a build error (but not for things > > marked CONFIG_BROKEN), an oops, a hang, data corruption, a real > > security issue, or some "oh, that's not good" issue. In short, something > > critical. > > - It or an equivalent fix must already exist in Linus' tree (upstream). > > > > I'm not sure if the problem "we can't get any hugepage in coredump" > > is considered as 'some "oh, that's not good" issue'. > > But yes, it's not a critical one. > > If you mean I violated the second rule, sorry, I'll get it into upstream first. > > The second rule is the clear one. If you are submitting a patch to > a subsystem maintainer and you want it to go into stable branches as > well, you must put 'Cc: stable@xxxxxxxxxxxxxxx' in the commit message, > not just the mail header. Got it. Thank you. Naoya -- 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>