From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the ftrace tree
Date: Mon, 24 Mar 2025 16:28:02 -0400 [thread overview]
Message-ID: <20250324162802.0fda49eb@gandalf.local.home> (raw)
In-Reply-To: <20250324133533.19b88cbf@canb.auug.org.au>
On Mon, 24 Mar 2025 13:35:33 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> In commit
>
> 6d5934331009 ("tracing: Do not use PERF enums when perf is not defined")
>
> Fixes tag
>
> Fixes: a1e3ad43115e ("tracing: Ensure module defining synth event cannot be unloaded while tracing")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
I rebased due to a conflict between my topic branches. Good thing too, as
it appears it also caught the fact that I cut and pasted the wrong commit
to fix :-p
>
> Did you mean
>
> Fixes: a1e3ad43115e ("tracing: Fix synth event printk format for str fields")
>
> or
>
> Fixes: 21581dd4e7ff ("tracing: Ensure module defining synth event cannot be unloaded while tracing")
Thanks,
-- Steve
next prev parent reply other threads:[~2025-03-24 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 2:35 linux-next: Fixes tag needs some work in the ftrace tree Stephen Rothwell
2025-03-24 20:28 ` Steven Rostedt [this message]
2025-03-24 20:29 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 23:52 Stephen Rothwell
2025-11-21 9:12 ` Tomas Glozar
2024-11-19 6:40 Stephen Rothwell
2024-11-19 14:00 ` Steven Rostedt
2024-03-17 21:35 Stephen Rothwell
2024-03-17 21:46 ` Steven Rostedt
2021-02-11 20:57 Stephen Rothwell
2021-02-11 21:21 ` Steven Rostedt
2021-02-11 21:27 ` Tom Zanussi
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=20250324162802.0fda49eb@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=sfr@canb.auug.org.au \
/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