From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
akpm@linux-foundation.org, mhiramat@kernel.org,
yujie.liu@intel.com, zhengyejian1@huawei.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tracing: Free buffers when a used dynamic event is removed" failed to apply to 4.19-stable tree
Date: Sun, 4 Dec 2022 19:57:26 -0500 [thread overview]
Message-ID: <Y41B9nmN0RL3RNYi@sashalap> (raw)
In-Reply-To: <Y4xYg2i7lS6z3eIe@kroah.com>
On Sun, Dec 04, 2022 at 09:21:23AM +0100, Greg KH wrote:
>On Sat, Dec 03, 2022 at 05:36:55PM -0500, Steven Rostedt wrote:
>> On Sat, 03 Dec 2022 12:20:15 +0100
>> <gregkh@linuxfoundation.org> wrote:
>>
>> > The patch below does not apply to the 4.19-stable tree.
>> > If someone wants it applied there, or to any other stable or longterm
>> > tree, then please email the backport, including the original git commit
>> > id to <stable@vger.kernel.org>.
>> >
>> > Possible dependencies:
>> >
>> > 4313e5a61304 ("tracing: Free buffers when a used dynamic event is removed")
>>
>> Hmm, isn't the above the patch that failed to apply?
>
>yes, tools are not the smartest at times :)
It's just what the script does: it always lists the commit we actually
want to apply, makes it easier for the rest of my scripts :)
--
Thanks,
Sasha
prev parent reply other threads:[~2022-12-05 0:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 11:20 FAILED: patch "[PATCH] tracing: Free buffers when a used dynamic event is removed" failed to apply to 4.19-stable tree gregkh
2022-12-03 22:36 ` Steven Rostedt
2022-12-04 8:21 ` Greg KH
2022-12-04 16:14 ` Steven Rostedt
2022-12-04 16:34 ` Greg KH
2023-03-10 19:52 ` Steven Rostedt
2023-03-11 8:47 ` Greg KH
2022-12-05 0:57 ` Sasha Levin [this message]
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=Y41B9nmN0RL3RNYi@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=yujie.liu@intel.com \
--cc=zhengyejian1@huawei.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