From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3y0w8s6GvgzDr4N for ; Mon, 25 Sep 2017 17:05:49 +1000 (AEST) Received: by mail-pf0-x241.google.com with SMTP id a7so3256402pfj.5 for ; Mon, 25 Sep 2017 00:05:49 -0700 (PDT) Date: Mon, 25 Sep 2017 16:05:42 +0900 From: Sergey Senozhatsky To: "Luck, Tony" Cc: Sergey Senozhatsky , Santosh Sivaraj , Sergey Senozhatsky , "Yu, Fenghua" , 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" Subject: Re: [RFC][PATCH v2 0/7] printk/ia64/ppc64/parisc64: let's deprecate %pF/%pf printk specifiers Message-ID: <20170925070542.GA387@jagdpanzerIV.localdomain> References: <20170920162910.32053-1-sergey.senozhatsky@gmail.com> <20170922053404.3zpfpwetabjut2er@santosiv.in.ibm.com> <20170922080023.GA599@jagdpanzerIV.localdomain> <3908561D78D1C84285E8C5FCA982C28F61381992@ORSMSX114.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F61381992@ORSMSX114.amr.corp.intel.com> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On (09/22/17 16:48), Luck, Tony wrote: [..] > Tested patch series on ia64 successfully. > > Tested-by: Tony Luck thanks! > After this goes upstream, you should submit a patch to get rid of > all uses of %pF (70 instances in 35 files) and %pf (63 in 34) > > Perhaps break the patch by top-level directory (e.g. get all the %pF > and %pF in the 17 files under drivers/ in one patch). frankly, I was going to have some sort of a lazy deprecation process: didn't plan to send out a patch set that would hunt down all pf/pF-s. hm... speaking of upstream, any objections if this patch set will go through the printk tree, in one piece? I'll wait for several more days and then resend v3 with updated Documentation and tweaked checkpatch warning message. -ss