From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: alexander.levin@verizon.com, dennisszhou@gmail.com,
tj@kernel.org, stable@vger.kernel.org,
stable-commits@vger.kernel.org
Subject: Re: Patch "percpu: don't forget to free the temporary struct pcpu_alloc_info" has been added to the 4.14-stable tree
Date: Thu, 21 Dec 2017 09:05:06 +0100 [thread overview]
Message-ID: <20171221080506.GB10992@kroah.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1712201332100.14337@knanqh.ubzr>
On Wed, Dec 20, 2017 at 01:41:01PM -0500, Nicolas Pitre wrote:
> On Wed, 20 Dec 2017, gregkh@linuxfoundation.org wrote:
>
> > This is a note to let you know that I've just added the patch titled
> >
> > percpu: don't forget to free the temporary struct pcpu_alloc_info
> > to the 4.14-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > percpu-don-t-forget-to-free-the-temporary-struct-pcpu_alloc_info.patch
> > and it can be found in the queue-4.14 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> If you consider this patch worthy enough for the stable tree, then you
> should also pick commit abee210500ed otherwise the CRIS architecture
> will regress.
Sadly, CRIS is dead, but yeah, it's not good to kill it earlier than
expected :)
I'll take Sasha's patch to drop this, thanks.
greg k-h
next prev parent reply other threads:[~2017-12-21 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 17:20 Patch "percpu: don't forget to free the temporary struct pcpu_alloc_info" has been added to the 4.14-stable tree gregkh
2017-12-20 18:41 ` Nicolas Pitre
2017-12-21 0:59 ` alexander.levin
2017-12-21 8:05 ` Greg KH [this message]
2017-12-21 22:40 ` Nicolas Pitre
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=20171221080506.GB10992@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@verizon.com \
--cc=dennisszhou@gmail.com \
--cc=nicolas.pitre@linaro.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@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).