From hch at lst.de  Fri Oct 18 17:28:39 2019
From: hch at lst.de (Christoph Hellwig)
Date: Fri, 18 Oct 2019 15:28:39 -0000
Subject: [Drbd-dev] [PATCH v2 00/33] Kill pr_warning in the whole linux
	code
In-Reply-To: <20191018142626.vmbgclelw23h5pdn@pathway.suse.cz>
References: <20191018031710.41052-1-wangkefeng.wang@huawei.com>
	<20191018142626.vmbgclelw23h5pdn@pathway.suse.cz>
Message-ID: <20191018152226.GA32150@lst.de>

As I said before: please just send Linus a scripted conversion after
the next -rc1.  There is no point in creating all this churn.

From joe at perches.com  Fri Oct 18 17:43:43 2019
From: joe at perches.com (Joe Perches)
Date: Fri, 18 Oct 2019 15:43:43 -0000
Subject: [Drbd-dev] [PATCH v2 00/33] Kill pr_warning in the whole linux
	code
In-Reply-To: <20191018152226.GA32150@lst.de>
References: <20191018031710.41052-1-wangkefeng.wang@huawei.com>
	<20191018142626.vmbgclelw23h5pdn@pathway.suse.cz>
	<20191018152226.GA32150@lst.de>
Message-ID: <86695bdf8e8e7425b680dcbcb23acec5e58853da.camel@perches.com>

(Adding Stephen Rothwell)

On Fri, 2019-10-18 at 17:22 +0200, Christoph Hellwig wrote:
> As I said before: please just send Linus a scripted conversion after
> the next -rc1.  There is no point in creating all this churn.	

I again ask for a scripted mechanism to be added to
-next to allow these types of scriptable patches to get
compilation coverage testing.