[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <628285fc7757f020159503d4d3b45790e73f0133.camel@perches.com>
Date: Fri, 27 Aug 2021 09:09:32 -0700
From: Joe Perches <joe@...ches.com>
To: Greg KH <gregkh@...uxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Rasmus Villemoes <linux@...musvillemoes.dk>,
linux-scsi@...r.kernel.org, storagedev@...rochip.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-staging@...ts.linux.dev
Subject: Re: [PATCH 0/5] vsprintf and uses: Add upper case output to %*ph
extension
On Fri, 2021-08-27 at 12:23 +0200, Greg KH wrote:
> On Fri, Aug 27, 2021 at 11:46:20AM +0300, Andy Shevchenko wrote:
> > On Fri, Aug 27, 2021 at 01:10:41AM -0700, Joe Perches wrote:
> > > On Fri, 2021-08-27 at 10:51 +0300, Andy Shevchenko wrote:
> > > > On Thu, Aug 26, 2021 at 11:43:00AM -0700, Joe Perches wrote:
> > > > > Several sysfs uses that could use %*ph are upper case hex output.
> > > > > Add a flag to the short hex formatting routine in vsprintf to support them.
> > > > > Add documentation too.
> > > >
> > > > Thanks!
> > > >
> > > > Unfortunately I have got only first patch and this cover letter. Can you,
> > > > please, Cc entire series?
> > >
> > > It's on lore.
> > >
> > > https://lore.kernel.org/lkml/cover.1630003183.git.joe@perches.com/T/#u
> >
> > Thanks. So, you won't me to review them in a regular way :-)
> >
> > TBH, I think those examples may pretty much be safe to use small
> > letters always.
>
> I agree, let's just fix the users here to use small letters instead of
> adding another modifier to the kernel.
ABI _should_ mean stability for random parsers.
I don't use these so I don't care that much.
Powered by blists - more mailing lists