public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
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, 18 Mar 2024 08:35:35 +1100	[thread overview]
Message-ID: <20240318083535.79501c6e@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

Hi all,

In commit

  2fd814ad5713 ("ring-buffer: Make wake once of ring_buffer_wait() more robust")

Fixes tag

  Fixes: 5b37b7eb98a19 ("ring-buffer: Make wake once of ring_buffer_wait() more robust")

has these problem(s):

  - Target SHA1 does not exist

The Fixes tag seems to be referring to the commit that contains the
Fixes tag :-(

Also, pleas keep all the commit message tags together at the end of the
commit message.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-03-17 21:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17 21:35 Stephen Rothwell [this message]
2024-03-17 21:46 ` linux-next: Fixes tag needs some work in the ftrace tree 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
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
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=20240318083535.79501c6e@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