From: Andrew Jones <andrew.jones@linux.dev>
To: Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [kvm-unit-tests PATCH] scripts/checkpatch.pl: Adjust the top_of_kernel_tree check for kvm-unit-tests
Date: Mon, 8 Sep 2025 13:39:46 -0500 [thread overview]
Message-ID: <20250908-3c28b520ea1cf3ffa7b03509@orel> (raw)
In-Reply-To: <20250724143258.52597-1-thuth@redhat.com>
On Thu, Jul 24, 2025 at 04:32:58PM +0200, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> The copy of checkpatch.pl that we currently have in the kvm-unit-tests
> repository refuses to work without the --no-tree switch, since it looks
> for some kernel-related files to determine the top directory. Adjust this
> list of files for the kvm-unit-tests repository to make it work.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> scripts/checkpatch.pl | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index acef47b7..e858261c 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1382,9 +1382,8 @@ sub top_of_kernel_tree {
> my ($root) = @_;
>
> my @tree_check = (
> - "COPYING", "CREDITS", "Kbuild", "MAINTAINERS", "Makefile",
> - "README", "Documentation", "arch", "include", "drivers",
> - "fs", "init", "ipc", "kernel", "lib", "scripts",
> + "COPYRIGHT", "LICENSE", "MAINTAINERS", "Makefile",
> + "README.md", "docs", "lib", "scripts",
> );
>
> foreach my $check (@tree_check) {
> --
> 2.50.1
>
Merged.
Thanks,
drew
prev parent reply other threads:[~2025-09-08 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 14:32 [kvm-unit-tests PATCH] scripts/checkpatch.pl: Adjust the top_of_kernel_tree check for kvm-unit-tests Thomas Huth
2025-09-08 17:14 ` Andrew Jones
2025-09-08 18:39 ` Andrew Jones [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=20250908-3c28b520ea1cf3ffa7b03509@orel \
--to=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=thuth@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