linux-kernel - checkpatch stops processing at an empty commit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 26 Sep 2022 13:41:53 +0300
From:   Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To:     Andy Whitcroft <apw@...onical.com>, Joe Perches <joe@...ches.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: checkpatch stops processing at an empty commit

Hi,

I use empty commits as "banner" commits, and it seems that checkpatch stops
processing commits when it encounters such an empty commit. This happens
both when using checkpatch for patch files and when using the -g option
to check the git branch.

Here I call checkpatch for a bigger range, in which the second commit
(4928b50c0e23) is an empty commit:

$ ./scripts/checkpatch.pl -g --strict --max-line-length=80 c553517a043b..aec2d6335383
---------------------------------------------------------
Commit 1bd2c75f1254 ("media: v4l2-subdev: Sort includes")
---------------------------------------------------------
total: 0 errors, 0 warnings, 0 checks, 24 lines checked

Commit 1bd2c75f1254 ("media: v4l2-subdev: Sort includes") has no obvious style problems and is ready for submission.
--------------------------------------------------------------------------------------
Commit 4928b50c0e23 ("=========================== Fixes ============================")
--------------------------------------------------------------------------------------

  Tomi