From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Jonathan Corbet <corbet@lwn.net>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: core-api/printk-formats.rst: Clarify formatting {cpu,node}mask
Date: Wed, 11 Nov 2020 18:48:16 +0200 [thread overview]
Message-ID: <20201111164816.GN4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201111152933.GA1702@alley>
On Wed, Nov 11, 2020 at 04:29:33PM +0100, Petr Mladek wrote:
> On Tue 2020-11-10 15:41:21, Geert Uytterhoeven wrote:
> > Clarify how to pass the field width for bitmaps, and mention the helper
> > macros that are available to ease printing cpumask and nodemask.
...
> %*pb 0779
> %*pbl 0,3-6,8-10
>
> For printing bitmap and its derivatives such as cpumask and nodemask.
>
> It takes two arguments, see '*'. The first argument defines the number
> of bits in the mask. The second argument points to the mask.
>
> %*pb outputs the bitmap as a hex number. If the size is bigger than 32-bit
> then 32-bit values are separated by a comma.
>
> %*pbl outputs the bitmap as a range list.
>
> The number of bits is passed by value. The mask is passed by reference.
It can be improved at least by replacing mask with bitmap here.
> Helper macros cpumask_pr_args() and nodemask_pr_args() are available to
> ease printing cpumask and nodemask.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-11-11 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:41 [PATCH] docs: core-api/printk-formats.rst: Clarify formatting {cpu,node}mask Geert Uytterhoeven
2020-11-11 15:29 ` Petr Mladek
2020-11-11 16:48 ` Andy Shevchenko [this message]
2020-11-13 22:04 ` Jonathan Corbet
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=20201111164816.GN4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/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).