From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: catalin.marinas@arm.com, rostedt@goodmis.org,
takahiro.akashi@linaro.org, will.deacon@arm.com,
stable@vger.kernel.org, stable-commits@vger.kernel.org,
sudeep.holla@arm.com
Subject: Re: Patch "arm64: kernel: pause/unpause function graph tracer in cpu_suspend()" has been added to the 4.1-stable tree
Date: Tue, 15 Mar 2016 08:04:39 -0700 [thread overview]
Message-ID: <20160315150439.GA12990@kroah.com> (raw)
In-Reply-To: <20160315140806.GA11376@red-moon>
On Tue, Mar 15, 2016 at 02:08:19PM +0000, Lorenzo Pieralisi wrote:
> Hi Greg,
>
> On Tue, Jan 26, 2016 at 10:54:50PM -0800, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > arm64: kernel: pause/unpause function graph tracer in cpu_suspend()
> >
> > to the 4.1-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:
> > arm64-kernel-pause-unpause-function-graph-tracer-in-cpu_suspend.patch
> > and it can be found in the queue-4.1 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.
>
> We have just noticed this patch did not make it to 3.18 stable kernel
> even though it was marked for #3.16+, probably it has slipped through
> the cracks, please let us know what we can do to get it applied
> to the 3.18 stable tree.
Why ask me, I'm not in charge of the 3.18 stable tree?
Hint, use https://www.kernel.org/category/releases.html in the future...
And do people really even use 3.18 for arm64 these days?
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-15 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 6:54 Patch "arm64: kernel: pause/unpause function graph tracer in cpu_suspend()" has been added to the 4.1-stable tree gregkh
2016-03-15 14:08 ` Lorenzo Pieralisi
2016-03-15 14:07 ` Steven Rostedt
2016-03-15 14:39 ` Lorenzo Pieralisi
2016-03-15 15:04 ` Greg KH [this message]
2016-03-15 16:28 ` Lorenzo Pieralisi
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=20160315150439.GA12990@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=catalin.marinas@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=rostedt@goodmis.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudeep.holla@arm.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
/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).