From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Jakub Kicinski <kuba@kernel.org>, Joe Perches <joe@perches.com>
Cc: csully@google.com, sagis@google.com, jonolson@google.com,
davem@davemloft.net, lrizzo@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] gve: Fix the size used in a 'dma_free_coherent()' call
Date: Mon, 3 Aug 2020 21:19:26 +0200 [thread overview]
Message-ID: <3a25ddc6-adaa-d17d-50f4-8f8ab2ed25eb@wanadoo.fr> (raw)
In-Reply-To: <20200803084106.050eb7f6@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Le 03/08/2020 à 17:41, Jakub Kicinski a écrit :
> On Sun, 2 Aug 2020 16:15:23 +0200 Christophe JAILLET wrote:
>> Update the size used in 'dma_free_coherent()' in order to match the one
>> used in the corresponding 'dma_alloc_coherent()'.
>>
>> Fixes: 893ce44df5 ("gve: Add basic driver framework for Compute Engine Virtual NIC")
>> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
> Fixes tag: Fixes: 893ce44df5 ("gve: Add basic driver framework for Compute Engine Virtual NIC")
> Has these problem(s):
> - SHA1 should be at least 12 digits long
> Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
> or later) just making sure it is not set (or set to "auto").
>
Hi,
I have git 2.25.1 and core.abbrev is already 12, both in my global
.gitconfig and in the specific .git/gitconfig of my repo.
I would have expected checkpatch to catch this kind of small issue.
Unless I do something wrong, it doesn't.
Joe, does it make sense to you and would one of the following patch help?
If I understand the regex correctly, I guess that checkpatch should
already spot such things. If correct, proposal 1 fix a bug.
If I'm wrong, proposal 2 adds a new test.
CJ
Proposal #1 : find what looks like a commit number, with 5+ char
(instead of 12+), before looking if it is looks like a standard layout
with expected length
===========
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index cc5542cc234f..f42b6a65f5c1 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2828,7 +2828,7 @@ sub process {
$line !~
/^\s*(?:Link|Patchwork|http|https|BugLink|base-commit):/i &&
$line !~ /^This reverts commit [0-9a-f]{7,40}/ &&
($line =~ /\bcommit\s+[0-9a-f]{5,}\b/i ||
- ($line =~ /(?:\s|^)[0-9a-f]{12,40}(?:[\s"'\(\[]|$)/i &&
+ ($line =~ /(?:\s|^)[0-9a-f]{5,40}(?:[\s"'\(\[]|$)/i &&
$line !~ /[\<\[][0-9a-f]{12,40}[\>\]]/i &&
$line !~ /\bfixes:\s*[0-9a-f]{12,40}/i))) {
my $init_char = "c";
Proposal #2 : add a specific and explicit check
===========
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index cc5542cc234f..13ecfbd38af3 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -2989,6 +2989,12 @@ sub process {
}
}
+# check for too short commit id
+ if ($in_commit_log && $line =~
/(^fixes:|\bcommit)\s+([0-9a-f]{0,11})\b/i) {
+ WARN("TOO_SHORT_COMMIT_ID",
+ "\"$1\" tag should be at least 12
chars long. $2 is only " . length($2) . " long\n" . $herecurr);
+ }
+
# ignore non-hunk lines and lines being removed
next if (!$hunk_line || $line =~ /^-/);
next prev parent reply other threads:[~2020-08-03 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 14:15 Christophe JAILLET
2020-08-03 15:41 ` Jakub Kicinski
2020-08-03 19:19 ` Christophe JAILLET [this message]
2020-08-03 19:35 ` Joe Perches
2020-08-03 19:50 ` Christophe JAILLET
2020-08-03 19:50 ` Christophe JAILLET
2020-08-04 7:16 ` Willem de Bruijn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a25ddc6-adaa-d17d-50f4-8f8ab2ed25eb@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=jonolson@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrizzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=sagis@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®