public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Petr Mladek <pmladek@suse.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: linux-next: Fixes tag needs some work in the printk tree
Date: Mon, 27 Jul 2020 17:13:44 +0206	[thread overview]
Message-ID: <87tuxt3sjj.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20200727234612.3037c4a5@canb.auug.org.au>

On 2020-07-27, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> In commit
>
>   96b917f8e9ec ("printk: ringbuffer: support dataless records")
>
> Fixes tag
>
>   Fixes: ("printk: use the lockless ringbuffer")
>
> has these problem(s):
>
>   - No SHA1 recognised
>
> Maybe you meant
>
> Fixes: 896fbe20b4e2 ("printk: use the lockless ringbuffer")

Yes, sorry. I did not think linux-next SHA1 hashes were used in commit
logs.

John Ogness

  reply	other threads:[~2020-07-27 15:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 13:46 linux-next: Fixes tag needs some work in the printk tree Stephen Rothwell
2020-07-27 15:07 ` John Ogness [this message]
2020-07-27 22:19   ` Stephen Rothwell
2020-07-28  1:22     ` Sergey Senozhatsky
  -- strict thread matches above, loose matches on Subject: below --
2025-11-23 21:53 Stephen Rothwell
2025-11-24 14:54 ` Petr Mladek
2021-07-11  3:01 Stephen Rothwell
2020-11-02 21:32 Stephen Rothwell
2020-11-03  8:46 ` Petr Mladek
2019-04-25 13:30 Stephen Rothwell
2019-04-26  7:37 ` Petr Mladek

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=87tuxt3sjj.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sergey.senozhatsky@gmail.com \
    --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