From: David Laight <david.laight.linux@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: helpdesk@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Create printk@lists.linux.dev
Date: Fri, 9 Oct 2026 15:26:27 +0100 [thread overview]
Message-ID: <20261009152627.285d814b@pumpkin> (raw)
In-Reply-To: <asjrq9g8EoUGepcH@pathway.suse.cz>
On Fri, 9 Oct 2026 15:27:07 +0200
Petr Mladek <pmladek@suse.com> wrote:
> Address : printk@lists.linux.dev
> Description: Linux printk and kernel string formatting development
> Owners : pmladek@suse.com, john.ogness@linutronix.de, andriy.shevchenko@linux.intel.com, rostedt@goodmis.org
> Allow HTML : N
> Archives : Y
>
> Reasons for the list and additional info:
>
> Honestly, the main motivation is to allow sending Sashiko review
> for changes in PRINTK and VSPRINTF subsystems as a reply to
> the mailing list.
There is also the smaller/faster printf code in 'nolibc'.
Might be worth mentioning that as well.
David
>
> I have discussed this with John at Plumbers conference. We both
> agree that Sashiko review is useful and often has to be addressed.
> It is much easier to reply a mail than searching for the review
> via the WebUI, copy/paste it to a mail, and comment on it.
>
> In addition, there are several people interested into printk and
> string formatting code. The mailing list would make it easier to get
> all interested people notified about new patches and problems
> in this area.
>
> That said, printk and string formatting are related only to some
> degree. The printk() code is more about tricks how to store
> the messages and show them in various context. While the string
> formatting is about tricky buffer manipulation and helpers for
> generating a human readable output of various data structures.
>
> There is only partial overlap of people interested into these
> two areas. Each group might deserve its own mailing list. But
> I would start simple with a common mailing list. We could always
> add another one when needed.
>
> Best Regards,
> Petr
next prev parent reply other threads:[~2026-10-09 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 13:27 Create printk@lists.linux.dev Petr Mladek
2026-10-09 14:26 ` David Laight [this message]
2026-10-09 15:00 ` Willy Tarreau
2026-10-09 17:34 ` David Laight
2026-10-09 17:36 ` Willy Tarreau
2026-10-13 6:50 ` Andy Shevchenko
2026-10-13 6:51 ` Andy Shevchenko
2026-10-19 15:02 ` Petr Mladek
2026-10-23 6:45 ` Chris Hoy Poy
2026-10-26 16:10 ` 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=20261009152627.285d814b@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=helpdesk@kernel.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.