From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Date: Thu, 23 Feb 2017 17:53:41 +0000 Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn Message-Id: <1487872421.14159.38.camel@perches.com> List-Id: References: <1487870304.14159.29.camel@perches.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Emil Velikov Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, Rob Herring , linux-omap , linux-scsi@vger.kernel.org, Richard Weinberger , tboot-devel@lists.sourceforge.net, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , sfi-devel@simplefirmware.org On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn Date: Thu, 23 Feb 2017 09:53:41 -0800 Message-ID: <1487872421.14159.38.camel@perches.com> References: <1487870304.14159.29.camel@perches.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, Rob Herring , linux-omap , linux-scsi@vger.kernel.org, Richard Weinberger , tboot-devel@lists.sourceforge.net, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , sfi-devel@simplefirmware.org, To: Emil Velikov Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: linux-crypto.vger.kernel.org On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn Date: Thu, 23 Feb 2017 09:53:41 -0800 Message-ID: <1487872421.14159.38.camel@perches.com> References: <1487870304.14159.29.camel@perches.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Emil Velikov Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, Rob Herring , linux-omap , linux-scsi@vger.kernel.org, Richard Weinberger , tboot-devel@lists.sourceforge.net, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , sfi-devel@simplefirmware.org List-Id: linux-ide@vger.kernel.org On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751508AbdBWRzF (ORCPT ); Thu, 23 Feb 2017 12:55:05 -0500 Received: from smtprelay0113.hostedemail.com ([216.40.44.113]:41803 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751125AbdBWRyG (ORCPT ); Thu, 23 Feb 2017 12:54:06 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: X-HE-Tag: touch62_3d837bf44f92c X-Filterd-Recvd-Size: 3946 Message-ID: <1487872421.14159.38.camel@perches.com> Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn From: Joe Perches To: Emil Velikov Cc: Rob Herring , "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, linux-scsi@vger.kernel.org, Richard Weinberger , sfi-devel@simplefirmware.org, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , tboot-devel@lists.sourceforge.net, oprofile-list@lists.sf.net, "linux-input@vger.kernel.org" , xen-devel@lists.xenproject.org, "linux-media@vger.kernel.org" , platform-driver-x86@vger.kernel.org, "devicetree@vger.kernel.org" , gigaset307x-common@lists.sourceforge.net, acpi4asus-user@lists.sourceforge.net, adi-buildroot-devel@lists.sourceforge.net, Pekka Paalanen , linux-omap , "linux-arm-kernel@lists.infradead.org" , netdev , Karol Herbst , "linux-kernel@vger.kernel.org" , linux-crypto@vger.kernel.org, linux-alpha@vger.kernel.org, Fabio Estevam , linuxppc-dev Date: Thu, 23 Feb 2017 09:53:41 -0800 In-Reply-To: References: <1487870304.14159.29.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.3-0ubuntu0.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtprelay0113.hostedemail.com ([216.40.44.113]:41803 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751125AbdBWRyG (ORCPT ); Thu, 23 Feb 2017 12:54:06 -0500 Message-ID: <1487872421.14159.38.camel@perches.com> Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn From: Joe Perches To: Emil Velikov Cc: Rob Herring , "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, linux-scsi@vger.kernel.org, Richard Weinberger , sfi-devel@simplefirmware.org, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , tboot-devel@lists.sourceforge.net, oprofile-list@lists.sf.net, "linux-input@vger.kernel.org" , xen-devel@lists.xenproject.org, "linux-media@vger.kernel.org" , platform-driver-x86@vger.kernel.org, "devicetree@vger.kernel.org" , gigaset307x-common@lists.sourceforge.net, acpi4asus-user@lists.sourceforge.net, adi-buildroot-devel@lists.sourceforge.net, Pekka Paalanen , linux-omap , "linux-arm-kernel@lists.infradead.org" , netdev , Karol Herbst , "linux-kernel@vger.kernel.org" , linux-crypto@vger.kernel.org, linux-alpha@vger.kernel.org, Fabio Estevam , linuxppc-dev Date: Thu, 23 Feb 2017 09:53:41 -0800 In-Reply-To: References: <1487870304.14159.29.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtprelay.hostedemail.com (smtprelay0052.hostedemail.com [216.40.44.52]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3vThgP6pVkzDqGh for ; Fri, 24 Feb 2017 04:53:53 +1100 (AEDT) Message-ID: <1487872421.14159.38.camel@perches.com> Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn From: Joe Perches To: Emil Velikov Cc: Rob Herring , "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , ML nouveau , Linux-ALSA , dri-devel , "open list:VIRTIO GPU DRIVER" , "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, linux-scsi@vger.kernel.org, Richard Weinberger , sfi-devel@simplefirmware.org, amd-gfx mailing list , "linux-acpi@vger.kernel.org" , tboot-devel@lists.sourceforge.net, oprofile-list@lists.sf.net, "linux-input@vger.kernel.org" , xen-devel@lists.xenproject.org, "linux-media@vger.kernel.org" , platform-driver-x86@vger.kernel.org, "devicetree@vger.kernel.org" , gigaset307x-common@lists.sourceforge.net, acpi4asus-user@lists.sourceforge.net, adi-buildroot-devel@lists.sourceforge.net, Pekka Paalanen , linux-omap , "linux-arm-kernel@lists.infradead.org" , netdev , Karol Herbst , "linux-kernel@vger.kernel.org" , linux-crypto@vger.kernel.org, linux-alpha@vger.kernel.org, Fabio Estevam , linuxppc-dev Date: Thu, 23 Feb 2017 09:53:41 -0800 In-Reply-To: References: <1487870304.14159.29.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable. From mboxrd@z Thu Jan 1 00:00:00 1970 From: joe@perches.com (Joe Perches) Date: Thu, 23 Feb 2017 09:53:41 -0800 Subject: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn In-Reply-To: References: <1487870304.14159.29.camel@perches.com> Message-ID: <1487872421.14159.38.camel@perches.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote: > On 23 February 2017 at 17:18, Joe Perches wrote: > > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote: > > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches wrote: > > > > There are ~4300 uses of pr_warn and ~250 uses of the older > > > > pr_warning in the kernel source tree. > > > > > > > > Make the use of pr_warn consistent across all kernel files. > > > > > > > > This excludes all files in tools/ as there is a separate > > > > define pr_warning for that directory tree and pr_warn is > > > > not used in tools/. > > > > > > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing. > > > > [] > > > Where's the removal of pr_warning so we don't have more sneak in? > > > > After all of these actually get applied, > > and maybe a cycle or two later, one would > > get sent. > > > > By which point you'll get a few reincarnation of it. So you'll have to > do the same exercise again :-( Maybe to one or two files. Not a big deal. > I guess the question is - are you expecting to get the series merged > all together/via one tree ? No. The only person that could do that effectively is Linus. > If not, your plan is perfectly reasonable.