From: Peter Maydell <peter.maydell@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
qemu-devel@nongnu.org, cohuck@redhat.com, berrange@redhat.com
Subject: Re: [PATCH v2] scripts/checkpatch: more checks on files imported from Linux
Date: Thu, 16 Jan 2025 10:58:22 +0000 [thread overview]
Message-ID: <CAFEAcA8npFet8ysFfRoPFdoJEZ-vY_58SvnPqQm7z5WKsHiRNA@mail.gmail.com> (raw)
In-Reply-To: <b6c50dd04d77d266a95d5752a24e97b65ccf3f05.camel@infradead.org>
On Thu, 16 Jan 2025 at 09:26, David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Thu, 2024-07-18 at 09:20 +0200, Stefano Garzarella wrote:
> > If a file imported from Linux is touched, emit a warning and suggest
> > using scripts/update-linux-headers.sh.
> >
> > Also check that updating imported files from Linux are not mixed with
> > other changes, in which case emit an error.
> >
> > Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>
> This now seems to complain about a commit which simply adds a file to
> update-linux-headers.sh and simultaneously adds the newly-imported
> file. Such as commit aa274c33c39e7de981dc195abe60e1a246c9d248.
>
> Was that the intent? Do we really need to have *three* separate
> commits, one for update-linux-headers.sh, one to import the new header,
> and then the third to add the QEMU code which actually uses the new
> header?
>
> $ scripts/checkpatch.pl 0001-update-linux-headers-import-linux-kvm_para.h-header.patch
> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> #36:
> new file mode 100644
>
> WARNING: added, moved or deleted file(s) imported from Linux, are you using scripts/update-linux-headers.sh?
> #41: FILE: include/standard-headers/linux/kvm_para.h:1:
> +/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
>
> ERROR: headers imported from Linux should be self-contained in a patch with no other changes
> #99: FILE: scripts/update-linux-headers.sh:63:
> -e 'linux/kernel' \
Just to state for the record the conclusion of our conversation
on IRC; yes, the error is correct. Header-imports from
Linux should be in a patch of their own which has no
changes except the results of running update-linux-headers.sh
(and ideally we would not have let aa274c33c39e7 through
code review). So, yes, you have a series of three patches:
* change update-linux-headers.sh
* automated-change-only commit resulting from running the script
* the change you want to make that requires the new header
thanks
-- PMM
prev parent reply other threads:[~2025-01-16 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 7:20 [PATCH v2] scripts/checkpatch: more checks on files imported from Linux Stefano Garzarella
2024-07-18 7:49 ` Daniel P. Berrangé
2024-07-19 12:05 ` Cornelia Huck
2024-08-07 8:53 ` Alex Bennée
2025-01-16 9:26 ` David Woodhouse
2025-01-16 10:58 ` Peter Maydell [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=CAFEAcA8npFet8ysFfRoPFdoJEZ-vY_58SvnPqQm7z5WKsHiRNA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=dwmw2@infradead.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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).