From: Sasha Levin <sashal@kernel.org>
To: Chris Redpath <Chris.Redpath@arm.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
nd <nd@arm.com>,
"pkondeti@codeaurora.org" <pkondeti@codeaurora.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Todd Kjos <tkjos@android.com>,
sudipm.mukherjee@gmail.com
Subject: Re: 4.14 stable missing 3054426dc68e "sched, trace: Fix prev_state output in sched_switch tracepoint"
Date: Sun, 17 Feb 2019 21:06:36 -0500 [thread overview]
Message-ID: <20190218020636.GT10616@sasha-vm> (raw)
In-Reply-To: <VI1PR08MB41429D8E68DC7B9D57FC3D40F8600@VI1PR08MB4142.eurprd08.prod.outlook.com>
On Fri, Feb 15, 2019 at 12:26:35PM +0000, Chris Redpath wrote:
>Hi Greg et al.
>
>A user of android-4.14 has pointed the following missing commit out.
>
>Commit 3054426dc68e ("sched, trace: Fix prev_state output in sched_switch tracepoint") was put into linux-4.20 around rc5 to fix an issue in a tracepoint. According to the patch itself, the broken commit was 3f5fe9fef5b2 ("sched/debug: Fix task state recording/printout") which was merged at what looks like 4.15-rc2. The broken commit was also picked for 4.14.64 as 13f12749af15 ("sched/debug: Fix task state recording/printout"). The fix (3054426dc68e) was pulled into 4.19. but was not called out as needing to go back to 4.14.
>
>Is it possible to pick 3054426dc68e ("sched, trace: Fix prev_state output in sched_switch tracepoint") for the next stable 4.14 release? If not I can do a backport for android-4.14, just let me know.
It wasn't backported because it didn't apply cleanly, since 4.4's
backport of 3f5fe9fef5b2 differs from Linus's tree.
The backport for that commit was done by Sudip (Cc'ed). I'll be happy to
take a backport of 3054426dc68e if someone sense one my way.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-02-18 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 12:26 4.14 stable missing 3054426dc68e "sched, trace: Fix prev_state output in sched_switch tracepoint" Chris Redpath
2019-02-18 2:06 ` Sasha Levin [this message]
2019-02-18 9:14 ` Sudip Mukherjee
2019-02-18 12:19 ` Greg KH
2019-02-18 12:34 ` Chris Redpath
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=20190218020636.GT10616@sasha-vm \
--to=sashal@kernel.org \
--cc=Chris.Redpath@arm.com \
--cc=nd@arm.com \
--cc=pkondeti@codeaurora.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tkjos@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.