From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the ftrace tree
Date: Mon, 24 Mar 2025 13:35:33 +1100 [thread overview]
Message-ID: <20250324133533.19b88cbf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
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")'
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")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-03-24 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 2:35 Stephen Rothwell [this message]
2025-03-24 20:28 ` linux-next: Fixes tag needs some work in the ftrace tree Steven Rostedt
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=20250324133533.19b88cbf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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