All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olaf Hering <olaf@aepfle.de>,
	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 jc_docs tree
Date: Tue, 04 Jul 2023 08:32:22 -0600	[thread overview]
Message-ID: <871qhniw7d.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230704094623.161dfdbc@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> In commit
>
>   c029b8a0c5d0 ("Fix documentation of panic_on_warn")
>
> Fixes tag
>
>   Fixes: 9e3961a0978 ("kernel: add panic_on_warn")
>
> has these problem(s):
>
>   - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 9e3961a09798 ("kernel: add panic_on_warn")

Apologies...I'll get this right one of these years...

Should be good now, thanks.

jon

  reply	other threads:[~2023-07-04 14:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 23:46 linux-next: Fixes tag needs some work in the jc_docs tree Stephen Rothwell
2023-07-04 14:32 ` Jonathan Corbet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-03 21:54 Stephen Rothwell
2022-03-28 20:58 Stephen Rothwell
2022-01-06 23:36 Stephen Rothwell
2022-01-07 10:25 ` James Clark
2022-01-07 16:19   ` Randy Dunlap
2022-01-10 10:30     ` James Clark
2022-01-07 16:35   ` Jonathan Corbet
2021-02-25 21:34 Stephen Rothwell
2021-02-25 21:39 ` Jonathan Corbet
2021-02-25 22:01   ` Stephen Rothwell
2021-02-25 22:35   ` Andrew Donnellan
2021-01-21 20:57 Stephen Rothwell
2019-05-20 21:44 Stephen Rothwell
2019-05-20 21:54 ` Jonathan Corbet
2019-05-21  7:18   ` Sven Eckelmann
2019-05-21 15:31     ` Jonathan Corbet
2019-05-21 18:23       ` Sven Eckelmann
2019-05-21 18:46         ` Jonathan Corbet
2019-05-21 18:52           ` Sven Eckelmann
2019-05-21 19:04             ` Jonathan Corbet
2019-05-21 19:05               ` Sven Eckelmann
2019-05-21  7:12 ` Sven Eckelmann

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=871qhniw7d.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.