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:18:24 -0800 Message-ID: <1487870304.14159.29.camel@perches.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Rob Herring Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , nouveau@lists.freedesktop.org, Linux-ALSA , dri-devel , virtualization@lists.linux-foundation.org, "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@lists.freedesktop.org, "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.k List-Id: amd-gfx.lists.freedesktop.org T24gVGh1LCAyMDE3LTAyLTIzIGF0IDA5OjI4IC0wNjAwLCBSb2IgSGVycmluZyB3cm90ZToKPiBP biBGcmksIEZlYiAxNywgMjAxNyBhdCAxOjExIEFNLCBKb2UgUGVyY2hlcyA8am9lQHBlcmNoZXMu Y29tPiB3cm90ZToKPiA+IFRoZXJlIGFyZSB+NDMwMCB1c2VzIG9mIHByX3dhcm4gYW5kIH4yNTAg dXNlcyBvZiB0aGUgb2xkZXIKPiA+IHByX3dhcm5pbmcgaW4gdGhlIGtlcm5lbCBzb3VyY2UgdHJl ZS4KPiA+IAo+ID4gTWFrZSB0aGUgdXNlIG9mIHByX3dhcm4gY29uc2lzdGVudCBhY3Jvc3MgYWxs IGtlcm5lbCBmaWxlcy4KPiA+IAo+ID4gVGhpcyBleGNsdWRlcyBhbGwgZmlsZXMgaW4gdG9vbHMv IGFzIHRoZXJlIGlzIGEgc2VwYXJhdGUKPiA+IGRlZmluZSBwcl93YXJuaW5nIGZvciB0aGF0IGRp cmVjdG9yeSB0cmVlIGFuZCBwcl93YXJuIGlzCj4gPiBub3QgdXNlZCBpbiB0b29scy8uCj4gPiAK PiA+IERvbmUgd2l0aCAnc2VkIHMvXGJwcl93YXJuaW5nXGIvcHJfd2Fybi8nIGFuZCBzb21lIGVt YWNzaW5nLgpbXQo+IFdoZXJlJ3MgdGhlIHJlbW92YWwgb2YgcHJfd2FybmluZyBzbyB3ZSBkb24n dCBoYXZlIG1vcmUgc25lYWsgaW4/CgpBZnRlciBhbGwgb2YgdGhlc2UgYWN0dWFsbHkgZ2V0IGFw cGxpZWQsCmFuZCBtYXliZSBhIGN5Y2xlIG9yIHR3byBsYXRlciwgb25lIHdvdWxkCmdldCBzZW50 LgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1k ZXZlbCBtYWlsaW5nIGxpc3QKWGVuLWRldmVsQGxpc3RzLnhlbi5vcmcKaHR0cHM6Ly9saXN0cy54 ZW4ub3JnL3hlbi1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Date: Thu, 23 Feb 2017 17:18:24 +0000 Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn Message-Id: <1487870304.14159.29.camel@perches.com> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rob Herring Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, SH-Linux , Alexander Shishkin , nouveau@lists.freedesktop.org, Linux-ALSA , dri-devel , virtualization@lists.linux-foundation.org, "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@lists.freedesktop.org, "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.k 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1487870304.14159.29.camel@perches.com> Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn From: Joe Perches To: Rob Herring Cc: Alexander Shishkin , Karol Herbst , Pekka Paalanen , Richard Weinberger , Fabio Estevam , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linuxppc-dev , tboot-devel@lists.sourceforge.net, nouveau@lists.freedesktop.org, oprofile-list@lists.sf.net, sfi-devel@simplefirmware.org, xen-devel@lists.xenproject.org, "linux-acpi@vger.kernel.org" , drbd-dev@lists.linbit.com, virtualization@lists.linux-foundation.org, linux-crypto@vger.kernel.org, "linux-ide@vger.kernel.org" , gigaset307x-common@lists.sourceforge.net, "linux-media@vger.kernel.org" , linux-omap , "linux-mtd@lists.infradead.org" , "devicetree@vger.kernel.org" , acpi4asus-user@lists.sourceforge.net, platform-driver-x86@vger.kernel.org, linux-scsi@vger.kernel.org, "linux-fbdev@vger.kernel.org" , Linux-ALSA , linux-alpha@vger.kernel.org, adi-buildroot-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org, SH-Linux , sparclinux@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel , "linux-input@vger.kernel.org" , netdev Date: Thu, 23 Feb 2017 09:18:24 -0800 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f174.google.com (mail-wr0-f174.google.com [209.85.128.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail09.linbit.com (LINBIT Mail Daemon) with ESMTPS id 95797105648E for ; Fri, 24 Feb 2017 15:59:48 +0100 (CET) Received: by mail-wr0-f174.google.com with SMTP id 89so14720275wrr.3 for ; Fri, 24 Feb 2017 06:59:48 -0800 (PST) Received: from soda.linbit ([86.59.100.100]) by smtp.gmail.com with ESMTPSA id 61sm10657436wrs.29.2017.02.24.06.59.47 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Feb 2017 06:59:47 -0800 (PST) Resent-Message-ID: <20170224145946.GV21236@soda.linbit> Received: from smtprelay.hostedemail.com (smtprelay0118.hostedemail.com [216.40.44.118]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail09.linbit.com (LINBIT Mail Daemon) with ESMTPS id 0E63E1056473 for ; Thu, 23 Feb 2017 18:18:40 +0100 (CET) Message-ID: <1487870304.14159.29.camel@perches.com> From: Joe Perches To: Rob Herring Date: Thu, 23 Feb 2017 09:18:24 -0800 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "linux-fbdev@vger.kernel.org" , linux-ia64@vger.kernel.org, Richard, SH-Linux , Alexander Shishkin , nouveau@lists.freedesktop.org, Linux-ALSA , dri-devel , virtualization@lists.linux-foundation.org, "linux-ide@vger.kernel.org" , "linux-mtd@lists.infradead.org" , sparclinux@vger.kernel.org, drbd-dev@lists.linbit.com, linux-scsi@vger.kernel.org, Weinberger , sfi-devel@simplefirmware.org, amd-gfx@lists.freedesktop.org, "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 Subject: Re: [Drbd-dev] [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn List-Id: "*Coordination* of development, patches, contributions -- *Questions* \(even to developers\) go to drbd-user, please." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: joe@perches.com (Joe Perches) Date: Thu, 23 Feb 2017 09:18:24 -0800 Subject: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn In-Reply-To: References: Message-ID: <1487870304.14159.29.camel@perches.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.