From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Tomas Glozar <tglozar@redhat.com>,
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: Fri, 21 Nov 2025 10:52:09 +1100 [thread overview]
Message-ID: <20251121105209.656f0e88@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Hi all,
In commit
f45a0cb29720 ("rtla/tests: Fix osnoise test calling timerlat")
Fixes tag
Fixes: 05b7e10687c ("tools/rtla: Add remaining support for osnoise actions")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
4b8e202c6fe0 ("rtla/tests: Extend action tests to 5s")
Fixes tags
Fixes: 4e26f84abfb ("rtla/tests: Add tests for actions")
Fixes: 05b7e10687c ("tools/rtla: Add remaining support for osnoise actions")
has these problem(s):
- SHA1 should be at least 12 digits long
This can be fixed for the future by setting core.abbrev to 12 (or
more) or (for git v2.11 or later) just making sure it is not set
(or set to "auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-11-20 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 23:52 Stephen Rothwell [this message]
2025-11-21 9:12 ` linux-next: Fixes tag needs some work in the ftrace tree Tomas Glozar
-- strict thread matches above, loose matches on Subject: below --
2025-03-24 2:35 Stephen Rothwell
2025-03-24 20:28 ` Steven Rostedt
2025-03-24 20:29 ` Steven Rostedt
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=20251121105209.656f0e88@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 \
--cc=tglozar@redhat.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