From: Thomas Gleixner <tglx@linutronix.de>
To: Petr Mladek <pmladek@suse.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jan Kara <jack@suse.cz>, Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] printk for 6.7
Date: Fri, 03 Nov 2023 00:02:16 +0100 [thread overview]
Message-ID: <877cmzlpxj.ffs@tglx> (raw)
In-Reply-To: <ZUPM1ZD6Q3mNOPaS@alley>
On Thu, Nov 02 2023 at 17:22, Petr Mladek wrote:
> Thomas Gleixner (7):
> printk: Add non-BKL (nbcon) console basic infrastructure
> printk: nbcon: Add acquire/release logic
> printk: nbcon: Add buffer management
> printk: nbcon: Add ownership state functions
> printk: nbcon: Add sequence handling
> printk: nbcon: Add emit function and callback function for atomic printing
> printk: nbcon: Allow drivers to mark unsafe regions and check state
TBH, I'm truly surprised to still see my name there as the author.
I definitely authored the early revisions and was influential on the
design, but comparing the final result to my initial hacked up POC
patches does not really reflect that.
It's probably too late to correct that, but I nevertheless want to make
it clear that:
John Ogness and Peter Mladek have been the ones who sorted out the
details and really should be those who get the credit.
Kodos to John and Peter for making this work!
Thanks,
Thomas
next prev parent reply other threads:[~2023-11-02 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 16:22 [GIT PULL] printk for 6.7 Petr Mladek
2023-11-02 23:02 ` Thomas Gleixner [this message]
2023-11-03 19:53 ` pr-tracker-bot
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=877cmzlpxj.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.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