From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Bradley Morgan <brads@mainlining.org>
Cc: john.ogness@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: Mon, 31 Aug 2026 10:22:37 +0200 [thread overview]
Message-ID: <20260831082237.lo_33Mqq@linutronix.de> (raw)
In-Reply-To: <E462DFFC-320A-48AA-90E3-B61B026BBC58@mainlining.org>
On 2026-08-31 08:31:22 [+0100], Bradley Morgan wrote:
> On 31 August 2026 07:36:48 BST, Sebastian Andrzej Siewior
> <bigeasy@linutronix.de> wrote:
> >On 2026-08-29 00:39:15 [+0100], Bradley Morgan wrote:
> >> Tested-by: Bradley Morgan <brads@mainlining.org> # PKVM, based on Pixel
> >7 (ARM64)
> >
> >Does this PKVM even use a nbcon and if so which one?
> >
>
> heh, not PKVM itself, I booted a kernel inside PKVM, which is the
> hypervisor, the kernel has nbcon inside. My T-B is for the kernel
That tested-by is futile if none of the suggested changes were actually
tested.
Sebastian
next prev parent reply other threads:[~2026-08-31 8:22 UTC|newest]
Thread overview: 13+ 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-31 15:01 ` Petr Mladek
2026-08-31 15:09 ` John Ogness
2026-09-01 7:40 ` Petr Mladek
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
2026-08-31 6:36 ` Sebastian Andrzej Siewior
2026-08-31 7:31 ` Bradley Morgan
2026-08-31 8:22 ` Sebastian Andrzej Siewior [this message]
2026-08-31 8:42 ` Bradley Morgan
2026-08-31 8:50 ` 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=20260831082237.lo_33Mqq@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=brads@mainlining.org \
--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®