From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: linux-kernel@vger.kernel.org, Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [BUG] checkpatch: false positive unwrapped commit description
Date: Sat, 20 Feb 2021 07:28:40 +0100 [thread overview]
Message-ID: <20210220062840.15846-1-xypron.glpk@gmx.de> (raw)
The next line leads to a false positive
Possible unwrapped commit description
(prefer a maximum 75 chars per line)
element type is ‘struct reg_info‘, not ‘u32‘ {aka ‘unsigned int‘}
+++++++++|+++++++++|+++++++++|+++++++++|+++++++++|+++++++++|+++++++++|
10 20 30 40 50 60 70
Unicode code point 0x2018 (‘) is counted as three characters
instead of one.
This code point is used in the GCC 11 warning sizeof-array-div.
Citing the warning verbatim lead to the observation.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
---
foo.txt | 0
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 foo.txt
diff --git a/foo.txt b/foo.txt
new file mode 100644
index 000000000000..e69de29bb2d1
--
2.30.0
reply other threads:[~2021-02-20 6:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210220062840.15846-1-xypron.glpk@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).