From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: Re: [RFC][PATCH v2 7/7] checkpatch: add pF/pf deprecation warning Date: Thu, 21 Sep 2017 09:27:17 +0900 Message-ID: <20170921002717.GA773@jagdpanzerIV.localdomain> References: <20170920162910.32053-1-sergey.senozhatsky@gmail.com> <20170920162910.32053-8-sergey.senozhatsky@gmail.com> <1505929138.12311.5.camel@perches.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: Sergey Senozhatsky , Tony Luck , Fenghua Yu , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , James Bottomley , Helge Deller , Petr Mladek , Steven Rostedt , Andrew Morton , Jessica Yu , Alexei Starovoitov , linux-ia64@vger.kernel.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Andy Whitcroft To: Joe Perches Return-path: In-Reply-To: <1505929138.12311.5.camel@perches.com> List-ID: List-Id: linux-parisc.vger.kernel.org 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 > + $ext_type = "Deprecated"; > + $use = " - use %pS instead"; > + $use =~ s/pS/ps/ if ($bad_extension =~ /pf/); ok, handy :) -ss