From: John Ogness <john.ogness@linutronix.de>
To: gregkh@linuxfoundation.org, gregkh@linuxfoundation.org,
pmladek@suse.com, sherry.sun@nxp.com, stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org
Subject: Re: Patch "printk: Avoid scheduling irq_work on suspend" has been added to the 6.18-stable tree
Date: Mon, 29 Dec 2025 13:21:25 +0106 [thread overview]
Message-ID: <877bu58owy.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <2025122945-trial-frosted-cef9@gregkh>
Hi Greg,
On 2025-12-29, <gregkh@linuxfoundation.org> wrote:
> This is a note to let you know that I've just added the patch titled
>
> printk: Avoid scheduling irq_work on suspend
>
> to the 6.18-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> printk-avoid-scheduling-irq_work-on-suspend.patch
> and it can be found in the queue-6.18 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
This patch should be accompanied with the preceeding commit:
d01ff281bd9b ("printk: Allow printk_trigger_flush() to flush all types")
and the later commit:
66e7c1e0ee08 ("printk: Avoid irq_work for printk_deferred() on suspend")
in order to completely avoid irq_work triggering during suspend for all
possible call paths.
John Ogness
next parent reply other threads:[~2025-12-29 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2025122945-trial-frosted-cef9@gregkh>
2025-12-29 12:15 ` John Ogness [this message]
2025-12-29 12:29 ` Patch "printk: Avoid scheduling irq_work on suspend" has been added to the 6.18-stable tree Greg KH
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=877bu58owy.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=pmladek@suse.com \
--cc=sherry.sun@nxp.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.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 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.