From: David Laight <david.laight.linux@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Petr Mladek <pmladek@suse.com>,
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 18:34:27 +0100 [thread overview]
Message-ID: <20261009183427.7a7d71ba@pumpkin> (raw)
In-Reply-To: <askBpT-dk59MzcTP@1wt.eu>
On Fri, 9 Oct 2026 17:00:53 +0200
Willy Tarreau <w@1wt.eu> wrote:
> On Fri, Oct 09, 2026 at 03:26:27PM +0100, David Laight wrote:
> > 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.
>
> Better not mix the two, nolibc is purely user land code and doesn't
> have the same constraints.
The kernel version is actually horrid, rewriting based (loosely) on the nolibc
version might be an improvement.
But I'm not sure how I could do it without it mostly being 'one big patch'.
The nolibc version is much more of an embedded system version and a usual libc one.
Things like not calling a function to add every character to the output help!
David
>
> Willy
next prev parent reply other threads:[~2026-10-09 17:34 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
2026-10-09 15:00 ` Willy Tarreau
2026-10-09 17:34 ` David Laight [this message]
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=20261009183427.7a7d71ba@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 \
--cc=w@1wt.eu \
/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.