From: Steven Rostedt <rostedt@goodmis.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Joe Perches <joe@perches.com>, Rob Herring <robh@kernel.org>,
Grant Likely <grant.likely@arm.com>
Subject: Re: [PATCH v1 2/3] lib/vsprintf: Replace custom spec to print decimals with generic one
Date: Fri, 31 Jul 2020 11:15:10 -0400 [thread overview]
Message-ID: <20200731111510.27c2ef73@oasis.local.home> (raw)
In-Reply-To: <20200731123145.22357-2-andriy.shevchenko@linux.intel.com>
On Fri, 31 Jul 2020 15:31:44 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> When printing phandle in %pOF the custom spec is used. First of all,
> it has SMALL flag which makes no sense for decimal numbers. Second,
> we have already default spec for decimal numbers. Use the latter in
> %pOF case as well.
The change log threw me off, as this is specifically for %pOFp. This
only affects the phandle ('p') portion. Please update the change log to
reflect that.
Also, I would add in Cc those that added this code and looked it over:
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Joe Perches <joe@perches.com>
Cc: Rob Herring <robh@kernel.org>
And mentioned in that code's change log:
Cc: Grant Likely <grant.likely@arm.com>
Otherwise,
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> lib/vsprintf.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index 8a8ac7ce0289..90d818ef03c5 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -1979,12 +1979,6 @@ char *device_node_string(char *buf, char *end, struct device_node *dn,
> char *buf_start = buf;
> struct property *prop;
> bool has_mult, pass;
> - static const struct printf_spec num_spec = {
> - .flags = SMALL,
> - .field_width = -1,
> - .precision = -1,
> - .base = 10,
> - };
>
> struct printf_spec str_spec = spec;
> str_spec.field_width = -1;
> @@ -2024,7 +2018,7 @@ char *device_node_string(char *buf, char *end, struct device_node *dn,
> str_spec.precision = precision;
> break;
> case 'p': /* phandle */
> - buf = number(buf, end, (unsigned int)dn->phandle, num_spec);
> + buf = number(buf, end, (unsigned int)dn->phandle, default_dec_spec);
> break;
> case 'P': /* path-spec */
> p = fwnode_get_name(of_fwnode_handle(dn));
next prev parent reply other threads:[~2020-07-31 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 12:31 [PATCH v1 1/3] lib/vsprintf: Replace hidden BUILD_BUG_ON() with static_assert() Andy Shevchenko
2020-07-31 12:31 ` [PATCH v1 2/3] lib/vsprintf: Replace custom spec to print decimals with generic one Andy Shevchenko
2020-07-31 15:15 ` Steven Rostedt [this message]
2020-07-31 15:48 ` Andy Shevchenko
2020-07-31 12:31 ` [PATCH v1 3/3] lib/vsprintf: Force type of flags for gfp_t Andy Shevchenko
2020-07-31 15:34 ` Steven Rostedt
2020-07-31 15:49 ` Andy Shevchenko
2020-07-31 16:04 ` Steven Rostedt
2020-07-31 14:38 ` [PATCH v1 1/3] lib/vsprintf: Replace hidden BUILD_BUG_ON() with static_assert() Steven Rostedt
2020-07-31 15:48 ` Andy Shevchenko
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=20200731111510.27c2ef73@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=grant.likely@arm.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pantelis.antoniou@konsulko.com \
--cc=pmladek@suse.com \
--cc=robh@kernel.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).