All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: John Ogness <john.ogness@linutronix.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 printk tree
Date: Mon, 24 Nov 2025 15:54:29 +0100	[thread overview]
Message-ID: <aSRxpRnLELpnxBQf@pathway.suse.cz> (raw)
In-Reply-To: <20251124085307.30709037@canb.auug.org.au>

On Mon 2025-11-24 08:53:07, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   863eb2c656b4 ("printk: Avoid irq_work for printk_deferred() on suspend")
> 
> Fixes tag
> 
>   Fixes: 26873eb26c45 ("printk: Avoid scheduling irq_work on suspend")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 26873e3e7f0c ("printk: Avoid scheduling irq_work on suspend")

Should be fixed now.

Thanks for report.

Best Regards,
Petr


  reply	other threads:[~2025-11-24 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-23 21:53 linux-next: Fixes tag needs some work in the printk tree Stephen Rothwell
2025-11-24 14:54 ` Petr Mladek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-11  3:01 Stephen Rothwell
2020-11-02 21:32 Stephen Rothwell
2020-11-03  8:46 ` Petr Mladek
2020-07-27 13:46 Stephen Rothwell
2020-07-27 15:07 ` John Ogness
2020-07-27 22:19   ` Stephen Rothwell
2020-07-28  1:22     ` Sergey Senozhatsky
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=aSRxpRnLELpnxBQf@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.