From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932973AbdIYHFt (ORCPT ); Mon, 25 Sep 2017 03:05:49 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:35376 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932517AbdIYHFr (ORCPT ); Mon, 25 Sep 2017 03:05:47 -0400 X-Google-Smtp-Source: AOwi7QBN+XhISwHNmtkrf8dUv1C8ikR2/batk+kK4KdWjs35V9GHH2whj77//Px6Uy04GvlpF739qA== 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 Content-Disposition: inline In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F61381992@ORSMSX114.amr.corp.intel.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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