From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] scripts/checkpatch: Fix a typo
Date: Tue, 4 Mar 2025 09:48:50 +0000 [thread overview]
Message-ID: <Z8bMgmWWtML2F9S9@redhat.com> (raw)
In-Reply-To: <20250303172508.93234-1-philmd@linaro.org>
On Mon, Mar 03, 2025 at 06:25:08PM +0100, 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
> ---
> scripts/checkpatch.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Urgh, sorry about that, thanks for fixing my messup.
>
> 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;
> --
> 2.47.1
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-03-04 9:49 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
2025-03-04 4:26 ` Stefan Hajnoczi
2025-03-04 9:48 ` Daniel P. Berrangé [this message]
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=Z8bMgmWWtML2F9S9@redhat.com \
--to=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 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).