From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: christophe leroy <christophe.leroy@c-s.fr>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 4.14 1/4] powerpc/mm/slice: Remove intermediate bitmap copy
Date: Sat, 10 Mar 2018 11:47:42 -0800 [thread overview]
Message-ID: <20180310194742.GA12279@kroah.com> (raw)
In-Reply-To: <84cf5fef-a940-cb2a-431e-5a550f725c4f@c-s.fr>
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
next prev parent reply other threads:[~2018-03-10 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 15:48 [PATCH 4.14 1/4] powerpc/mm/slice: Remove intermediate bitmap copy Christophe Leroy
2018-03-09 15:49 ` [PATCH 4.14 2/4] powerpc/mm/slice: create header files dedicated to slices Christophe Leroy
2018-03-09 15:49 ` [PATCH 4.14 3/4] powerpc/mm/slice: Enhance for supporting PPC32 Christophe Leroy
2018-03-09 15:49 ` [PATCH 4.14 4/4] powerpc/mm/slice: Fix hugepage allocation at hint address on 8xx Christophe Leroy
2018-03-10 0:10 ` [PATCH 4.14 1/4] powerpc/mm/slice: Remove intermediate bitmap copy Greg Kroah-Hartman
2018-03-10 7:27 ` christophe leroy
2018-03-10 14:52 ` Greg Kroah-Hartman
2018-03-10 16:14 ` christophe leroy
2018-03-10 19:47 ` Greg Kroah-Hartman [this message]
2018-03-13 13:24 ` Michael Ellerman
2018-05-31 8:54 Christophe Leroy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180310194742.GA12279@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).