[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18d9f8d6803c8957ec091c207780c163af07e41f.camel@perches.com>
Date: Fri, 27 Aug 2021 01:08:10 -0700
From: Joe Perches <joe@...ches.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] vsprintf/Documentation: Add X to %*ph extension to
output upper case hex
On Fri, 2021-08-27 at 10:48 +0300, Andy Shevchenko wrote:
> On Thu, Aug 26, 2021 at 11:43:01AM -0700, Joe Perches wrote:
> > A few sysfs output uses of hex arrays are uppercase and are nominally ABI.
> >
> > Add a mechanism to the existing vsprintf %*ph hex output extension to
> > support upper case hex output.
>
> ...
>
> > + The preferred output is lowercase
> > %*ph 00 01 02 ... 3f
> > %*phC 00:01:02: ... :3f
> > %*phD 00-01-02- ... -3f
> > %*phN 000102 ... 3f
> > + Formats with X are uppercase, used for backwards compatibility
> > + %*phX 00 01 02 ... 3F
> > + %*phCX 00:01:02: ... :3F
> > + %*phDX 00-01-02- ... -3F
> > + %*phNX 000102 ... 3F
>
> Why not using %*pH...?
I find X more intelligible.
> > + char locase = 0x20; /* ASCII OR'd for lower case see: number() */
>
> If you use h vs H, you may derive this from (fmt[...] & SMALL).
It's not necessary to use any more of the rather limited vsprintf
extension namespace.
Powered by blists - more mailing lists