From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-input@vger.kernel.org, Nick Dyer <nick@shmanahar.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: synaptics-rmi4 - use %ph to form F34 configuration ID
Date: Tue, 30 May 2017 12:17:22 -0700 [thread overview]
Message-ID: <1496171842.2618.30.camel@perches.com> (raw)
In-Reply-To: <1496171059.28981.33.camel@linux.intel.com>
On Tue, 2017-05-30 at 22:04 +0300, Andy Shevchenko wrote:
> On Tue, 2017-05-30 at 10:23 -0700, Joe Perches wrote:
> > On Tue, 2017-05-30 at 09:59 -0700, Dmitry Torokhov wrote:
> > > On Tue, May 30, 2017 at 10:23:58AM +0200, Benjamin Tissoires wrote:
> > > > On May 29 2017 or thereabouts, Dmitry Torokhov wrote:
> > > > >
> > > Or we'd need to introduce %pH I guess.
> >
> > As it's debugging output, I'd hazard to guess it doesn't matter.
> >
> > If someone _really_ needs upper-case output in *ph,
>
> Starting from the same...
> >
> > A pity that %ph[cdnCDN] isn't possible as that's the style used
> > by %pU[blBL] for lower/upper case output.
> >
> > There are < 80 uses of %[\*\d]+ph[CDN], maybe it'd be reasonable
> > to do a treewide sed to lowercase for them. Dunno.
It's more like ~300 when the grep is done properly,
-E needed to be -P, so I believe that's too many to
bother with a treewide sed.
> And I think less intrusive would be
> %pH[CDN]
> since the latter proposal misses plain %*ph use.
No it wouldn't necessarily.
%*phU could still be upper case too.
> But for now I would rather avoid it at all, I'm pretty sure there very
> rare cases when one needs
> 1) to print a dump, *and*
> 2) it should be upper cased.
Doubtful, but maybe there is a seq_ use somewhere
that could be converted.
Anyway I think the proposed change in the original
patch is fine and nothing else needs to be done.
next prev parent reply other threads:[~2017-05-30 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 4:49 [PATCH] Input: synaptics-rmi4 - use %ph to form F34 configuration ID Dmitry Torokhov
2017-05-30 8:23 ` Benjamin Tissoires
2017-05-30 16:59 ` Dmitry Torokhov
2017-05-30 17:23 ` Joe Perches
2017-05-30 19:04 ` Andy Shevchenko
2017-05-30 19:17 ` Joe Perches [this message]
2017-05-31 21:11 ` Nick Dyer
2017-06-02 5:10 ` Dmitry Torokhov
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=1496171842.2618.30.camel@perches.com \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.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