From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Bradley Morgan <brads@mainlining.org>,
brauner@kernel.org, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
lkp@intel.com, oe-lkp@lists.linux.dev, oleg@redhat.com,
oliver.sang@intel.com, ptikhomirov@virtuozzo.com,
rostedt@goodmis.org, senozhatsky@chromium.org
Subject: Re: [PATCH] nbcon/reboot: Flush nbcon consoles synchronously on reboot
Date: Fri, 9 Oct 2026 12:52:24 +0200 [thread overview]
Message-ID: <20261009105224.FgfdSrKA@linutronix.de> (raw)
In-Reply-To: <asixA20sG8QHH7hf@pathway.suse.cz>
On 2026-10-09 11:16:51 [+0200], Petr Mladek wrote:
> > Hi, this looks good to me reboot.c ended! :)
> >
> > Reviewed-by: Bradley Morgan <brads@mainlining.org>
>
> Honestly, I am more or less ignoring Reviewed-by: Bradley Morgan.
> I can't recall any problem reported by this person. And the excited,
> AI-generated, acks do not add much value.
to be fair, there is one:
| $ git log --grep "Reported-by: Bradley Morgan" --oneline | wc -l
| 1
and there are even fixes:
| $ git log --author "Bradley Morgan" --grep "Fixes:" --oneline | wc -l
| 12
> > That's ok :) I'm too unlucky as to not go to any conferences :c
>
> I am not sure if there will be any conferences when robots will
> be ready to attend them.
Would you or would not exclude Lieutenant Commander Data from a
conference? We don't have positronic brains yet but maybe in a few years
:)
> Best Regards,
> Petr
Sebastian
next prev parent reply other threads:[~2026-10-09 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 15:08 Petr Mladek
2026-10-08 15:19 ` Bradley Morgan
2026-10-09 9:16 ` Petr Mladek
2026-10-09 10:52 ` Sebastian Andrzej Siewior [this message]
2026-10-09 6:51 ` Sebastian Andrzej Siewior
2026-10-09 9:08 ` Petr Mladek
2026-10-09 12:59 ` Sebastian Andrzej Siewior
2026-10-09 13:28 ` John Ogness
2026-10-09 15:27 ` 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=20261009105224.FgfdSrKA@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=brads@mainlining.org \
--cc=brauner@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=oliver.sang@intel.com \
--cc=pmladek@suse.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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®