[Linux-kernel-mentees] [PATCH v2] checkpatch: handle line break between commit and hash value

Lukas Bulwahn lukas.bulwahn at gmail.com
Sun Sep 13 11:01:33 UTC 2020

On Sat, 12 Sep 2020, Ayush wrote:

> September 12, 2020 9:09 PM, "Ayush" <ayush at disroot.org> wrote:
> > I am re-evaluating my output and will give you a analysis of all commits
> > which are getting affected by my patch.
> > It will take time to run checkpatch.pl again on those commits, so I will
> > share as soon as it's finished.
> I fixed my script used for analysis and re-evaluated the affect of my patch.
> I have made a list of commits which are fixed with this patch, It can be found here:
> https://gist.githubusercontent.com/eldraco19/e7bf729b04cf6e2eee6ec52785b318d4/raw/74e13760fe01deee3285a1ec047ea0ac036cae76/commit_report.txt

Did checkpatch.pl output on other types change?

One of the testers on this list reported that two COMMIT_LOG_LONG_LINE 
reports disappeared. That should not have happened, right?

I had a look at the checkpatch.pl output for commit 0a2bd55c194a ("dm 
integrity: document allow_discard option").

I think the reported line is wrong here.

Also, the line number for other cases have changed.

Generally, the line number should point to the line where the error really 


More information about the Linux-kernel-mentees mailing list