From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Mladek <pmladek@suse.com>
Cc: John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Chris Down <chris@chrisdown.name>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Make John PRINTK co-maintainer
Date: Wed, 14 Oct 2026 09:16:18 -0400 [thread overview]
Message-ID: <20261014091618.673d6e67@gandalf.local.home> (raw)
In-Reply-To: <20261014115029.203908-1-pmladek@suse.com>
On Wed, 14 Oct 2026 13:50:29 +0200
Petr Mladek <pmladek@suse.com> wrote:
> John is author of the huge rework of the printk subsystem. He has a deep
> understanding of the code and great awareness of the various user
> expectations. He is willing to step into the maintainer role which
> will be a great help.
>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f53047aa8d3c..5dec288729ba 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -21848,8 +21848,8 @@ F: scripts/Makefile.propeller
>
> PRINTK
> M: Petr Mladek <pmladek@suse.com>
> +M: John Ogness <john.ogness@linutronix.de>
> R: Steven Rostedt <rostedt@goodmis.org>
> -R: John Ogness <john.ogness@linutronix.de>
> R: Sergey Senozhatsky <senozhatsky@chromium.org>
> S: Maintained
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git
Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2026-10-14 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 11:50 Petr Mladek
2026-10-14 12:02 ` John Ogness
2026-10-14 13:16 ` Steven Rostedt [this message]
2026-10-15 3:51 ` Sergey Senozhatsky
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=20261014091618.673d6e67@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris@chrisdown.name \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--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®