linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Jonathan Corbet <corbet@lwn.net>,
	phone-devel@vger.kernel.org, linux-doc@vger.kernel.org,
	Luca Weiss <luca.weiss@fairphone.com>,
	linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH] vsprintf/doc: Document format flags including field width and precision
Date: Wed, 24 May 2023 10:14:20 +0206	[thread overview]
Message-ID: <877csyjgnf.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <20230522150853.30417-1-pmladek@suse.com>

On 2023-05-22, Petr Mladek <pmladek@suse.com> wrote:
> +Examples::

> +	printk("Dynamic table: |%*d|%*s|\n", id_width, id, max_name_len, name);

> +	printk("Dynamic precision: %.*f\n", precision, value);

Generally speaking, it is rare to use printk() without a loglevel
specified. And it is preferred that the pr_ or dev_ macros are
used. Perhaps the examples should call pr_info() instead?

John Ogness

      parent reply	other threads:[~2023-05-24  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  6:52 [PATCH] docs: printk-formats: Clarify %*pb format parameters Luca Weiss
2023-05-17 16:19 ` Andy Shevchenko
2023-05-22  6:41   ` Luca Weiss
2023-05-22 15:08     ` [PATCH] vsprintf/doc: Document format flags including field width and precision Petr Mladek
2023-05-22 21:04       ` Rasmus Villemoes
2023-05-24  8:08       ` John Ogness [this message]

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=877csyjgnf.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=luca.weiss@fairphone.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=pmladek@suse.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;
as well as URLs for NNTP newsgroup(s).