[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1505960913.12311.18.camel@perches.com>
Date: Wed, 20 Sep 2017 19:28:33 -0700
From: Joe Perches <joe@...ches.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Tony Luck <tony.luck@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
James Bottomley <jejb@...isc-linux.org>,
Helge Deller <deller@....de>, Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jessica Yu <jeyu@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
linux-ia64@...r.kernel.org, linux-parisc@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Andy Whitcroft <apw@...onical.com>
Subject: Re: [RFC][PATCH v2 7/7] checkpatch: add pF/pf deprecation warning
On Thu, 2017-09-21 at 09:27 +0900, Sergey Senozhatsky wrote:
> On (09/20/17 10:38), Joe Perches wrote:
> > On Thu, 2017-09-21 at 01:29 +0900, Sergey Senozhatsky wrote:
> > > We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart
> > > enough to handle function pointer dereference on platforms where such
> > > dereference is required.
> > >
> > > checkpatch warning example:
> > >
> > > WARNING: Use '%pS/%ps' instead. This pointer extension was deprecated: '%pF'
> >
> > If this series is accepted, I think this message
> > is unclear and would prefer something like:
>
> sure, can tweak the patch.
>
> [..]
> > if ($bad_extension ne "") {
> > my $stat_real = raw_line($linenr, 0);
> > + my $ext_type = "Invalid";
> > + my $use = "";
> > for (my $count = $linenr + 1; $count <= $lc; $count++) {
> > $stat_real = $stat_real . "\n" . raw_line($count, 0);
> > }
> > + if ($bad_extension =~ /p[Ff]/i) {
>
> I think /i is not necessary here
You are right, it's not.
Powered by blists - more mailing lists