Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <ff96be1b-b1d6-f170-d8f3-6199945500ef@ideasonboard.com>
Date:   Mon, 26 Sep 2022 13:41:53 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Content-Language: en-US
To:     Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
From:   Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: checkpatch stops processing at an empty commit
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

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