On Sat, Mar 10, 2018 at 05:14:22PM +0100, christophe leroy wrote: > > > Le 10/03/2018 à 15:52, Greg Kroah-Hartman a écrit : > > On Sat, Mar 10, 2018 at 08:27:54AM +0100, christophe leroy wrote: > > > > > > > > > Le 10/03/2018 à 01:10, Greg Kroah-Hartman a écrit : > > > > On Fri, Mar 09, 2018 at 04:48:59PM +0100, Christophe Leroy wrote: > > > > > Upstream 326691ad4f179e6edc7eb1271e618dd673e4736d > > > > > > > > There is no such git commit id in Linus's tree :( > > > > > > > > Please fix up and resend the series. > > > > > > I checked again, it is there > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/powerpc/mm/slice.c?h=next-20180309&id=326691ad4f179e6edc7eb1271e618dd673e4736d > > > > That is linux-next, which has everything and the kitchen sink. It is > > not Linus's tree. Please wait for these things to be merged into > > Linus's tree before asking for the to be merged into the stable tree. > > That's a requirement. > > > > Oops, sorry, I thought everything on kernel.org was official. That would be a whole lot of "official" :) Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for what the rules are here, if you haven't already. > Once it is in, do I resend the patches or do I just ping you ? You would need to resend the patches (if they need backporting manually), or just send a list of the git commit ids that are needed to be applied (usually easier.) Also, why were these patches not tagged with the stable tag to start with? That way they would be automatically included in the stable tree when they hit Linus's tree. thanks, greg k-h