From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033441AbdI0FBz (ORCPT ); Wed, 27 Sep 2017 01:01:55 -0400 Received: from ozlabs.org ([103.22.144.67]:50283 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031840AbdI0FBs (ORCPT ); Wed, 27 Sep 2017 01:01:48 -0400 From: Michael Ellerman To: Sergey Senozhatsky , "Luck\, Tony" Cc: Sergey Senozhatsky , Santosh Sivaraj , Sergey Senozhatsky , "Yu\, Fenghua" , Benjamin Herrenschmidt , Paul Mackerras , 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 In-Reply-To: <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> <20170925070542.GA387@jagdpanzerIV.localdomain> User-Agent: Notmuch/0.21 (https://notmuchmail.org) Date: Wed, 27 Sep 2017 15:01:43 +1000 Message-ID: <871smsg2fc.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sergey Senozhatsky writes: > 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... That never works though, we have lots of cruft left over from times when that's happened and the conversion never quite got finished. At least if you send out the patches to do the removal they might eventually get merged. > speaking of upstream, any objections if this patch set will go through > the printk tree, in one piece? Do you mind putting it in a topic branch (based on rc2) and then merge that into the printk tree? That way I can merge the topic branch iff there are conflicts later down the line towards 4.15. cheers