[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875yulj4m8.fsf@meer.lwn.net>
Date: Mon, 27 Sep 2021 11:43:59 -0600
From: Jonathan Corbet <corbet@....net>
To: Utkarsh Verma <utkarshverma294@...il.com>,
Dwaipayan Ray <dwaipayanray1@...il.com>
Cc: Lukas Bulwahn <lukas.bulwahn@...il.com>,
Joe Perches <joe@...ches.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Utkarsh Verma <utkarshverma294@...il.com>
Subject: Re: [PATCH] Documentation: checkpatch: Document some more message
types
Utkarsh Verma <utkarshverma294@...il.com> writes:
> Added and documented 3 new message types:
> - UNNECESSARY_INT
> - UNSPECIFIED_INT
> - UNNECESSARY_ELSE
>
> Signed-off-by: Utkarsh Verma <utkarshverma294@...il.com>
> ---
> Documentation/dev-tools/checkpatch.rst | 47 ++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
So...when you send multiple patches with the same subject line that's
always a bad sign. We really want a "git --oneline" listing to give a
good idea of what the patch does, and that depends on more descriptive
subject lines.
In this case, something like:
docs: checkpatch: add UNNECESSARY/UNSPECIFIED_INT and UNNECESSARY_ELSE
I can fix up these two patches, but please try to keep this in mind for
future work.
(applying the patches now).
Thanks,
jon
Powered by blists - more mailing lists