mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bradley Morgan <brads@mainlining.org>
To: john.ogness@linutronix.de
Cc: bigeasy@linutronix.de, gregkh@linuxfoundation.org,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	pmladek@suse.com, rostedt@goodmis.org, senozhatsky@chromium.org,
	tglx@kernel.org, thierry.reding@kernel.org
Subject: Re: [PATCH printk v2 0/2] nbcon irq_work fixes
Date: Sat, 29 Aug 2026 00:39:15 +0100	[thread overview]
Message-ID: <6CCFF45A-3C60-4A38-BF22-7BA556DF28C0@mainlining.org> (raw)
In-Reply-To: <20260828140218.232439-1-john.ogness@linutronix.de>

On 28 August 2026 15:02:07 BST, John Ogness <john.ogness@linutronix.de>
wrote:
>Hi,
>
>This is v2 of a series to address some irq_work issues with nbcon.
>Initially motivated as a workaround for hardware-related regressions
>reported [0], it turns out that the workaround is actually a nice
>improvement for nbcon deferred printing in general.
>
>v1 is here [1].
>
>John Ogness
>
>The changes since v1:
>
>- Add a preceding patch to flush the irq_work on nbcon_free(). This
>  pre-existing issue was reported [2] by Sashiko while it was
>  reviewing v1.
>
>[0]
>https://lore.kernel.org/lkml/f3757a75-0ba1-4558-bf57-f19ab7e59a4c@nvidia.com
>[1]
>https://lore.kernel.org/lkml/20260827184750.203521-1-john.ogness@linutronix.de
>[2]
>https://sashiko.dev/#/patchset/20260827184750.203521-1-john.ogness%40linutronix.de
>
>John Ogness (2):
>  printk/nbcon: Flush nbcon_irq_work in nbcon_free()
>  printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY
>
> kernel/printk/nbcon.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>
>base-commit: ffe0486b139e45cd9c9ca2584f04a1910fe4f8a6
>
Tested-by: Bradley Morgan <brads@mainlining.org> # PKVM, based on Pixel 7 (ARM64)



--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/

      parent reply	other threads:[~2026-08-28 23:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 14:02 John Ogness
2026-08-28 14:02 ` [PATCH printk v2 1/2] printk/nbcon: Flush nbcon_irq_work in nbcon_free() John Ogness
2026-08-28 14:02 ` [PATCH printk v2 2/2] printk/nbcon: Change nbcon_irq_work to IRQ_WORK_LAZY John Ogness
2026-08-28 15:36 ` [PATCH printk v2 0/2] nbcon irq_work fixes Jon Hunter
2026-08-28 23:39 ` Bradley Morgan [this message]

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=6CCFF45A-3C60-4A38-BF22-7BA556DF28C0@mainlining.org \
    --to=brads@mainlining.org \
    --cc=bigeasy@linutronix.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.ogness@linutronix.de \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@kernel.org \
    --cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®