[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f5679b4c76bf0e16064f3a45319bc35938ad96b.camel@perches.com>
Date: Sun, 26 Jul 2020 09:42:06 -0700
From: Joe Perches <joe@...ches.com>
To: SeongJae Park <sj38.park@...il.com>
Cc: Michał Mirosław <mirq-linux@...e.qmqm.pl>,
SeongJae Park <sjpark@...zon.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, apw@...onical.com,
colin.king@...onical.com, jslaby@...e.cz, pavel@....cz,
SeongJae Park <sjpark@...zon.de>
Subject: Re: Re: Re: Re: Re: checkpatch: support deprecated terms checking
On Sun, 2020-07-26 at 17:36 +0200, SeongJae Park wrote:
> On Sun, 26 Jul 2020 07:50:54 -0700 Joe Perches <joe@...ches.com> wrote:
[]
> > I do not want to encourage relatively inexperienced people
> > to run checkpatch and submit inappropriate patches.
>
> Me, neither. But, I think providing more warnings and references is better for
> that.
Unfortunately, the inexperienced _do_ in fact run
checkpatch on files and submit inappropriate patches.
It's generally a time sink for the experienced
maintainers to reply.
> Simply limiting checks could allow people submitting inappropriate patches
> intorducing new uses of deprecated terms.
Tradeoffs...
I expect that patches being reviewed by maintainers
are preferred over files being inappropriately changed
by the inexperienced.
Those inappropriate changes should not be encouraged
by tools placed in the hands of the inexperienced.
Powered by blists - more mailing lists