From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH] scripts/checkpatch: Fix a typo
Date: Mon, 03 Mar 2025 20:39:16 +0100 [thread overview]
Message-ID: <8734ft3nvf.fsf@pond.sub.org> (raw)
In-Reply-To: <114e31e0-2085-4843-9ef2-3539d53eefd5@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 3 Mar 2025 18:35:06 +0100")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 3/3/25 18:25, Philippe Mathieu-Daudé wrote:
>> When running checkpatch.pl on a commit adding a file without
>> SPDX tag we get:
>> Undefined subroutine &main::WARNING called at ./scripts/checkpatch.pl line 1694.
>> The WARNING level is reported by the WARN() method. Fix the typo.
>> Fixes: fa4d79c64da ("scripts: mandate that new files have SPDX-License-Identifier")
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> Possible candidate to apply on /master as buildfix
>
> buildfix: because otherwise everybody running checkpatch and adding
> new file without SPDX tag will have to debug checkpatch.pl.
>
>> ---
>> scripts/checkpatch.pl | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
>> index 83b59fb4436..6ae9d7febee 100755
>> --- a/scripts/checkpatch.pl
>> +++ b/scripts/checkpatch.pl
>> @@ -1691,8 +1691,8 @@ sub process {
>> "'SPDX-License-Identifer'");
>> } else {
>> # Other files MAY have SPDX license if appropriate
>> - WARNING("Does new file '$expect_spdx_file' need " .
>> - "'SPDX-License-Identifer'?");
>> + WARN("Does new file '$expect_spdx_file' need " .
>> + "'SPDX-License-Identifer'?");
>> }
>> }
>> $expect_spdx = 1;
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2025-03-03 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 17:25 [PATCH] scripts/checkpatch: Fix a typo Philippe Mathieu-Daudé
2025-03-03 17:35 ` Philippe Mathieu-Daudé
2025-03-03 19:39 ` Markus Armbruster [this message]
2025-03-04 4:26 ` Stefan Hajnoczi
2025-03-04 9:48 ` Daniel P. Berrangé
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=8734ft3nvf.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.