linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giovanni Gherdovich <ggherdovich@suse.cz>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Giovanni Gherdovich <ggherdovich@suse.cz>
Subject: [PATCH] checkpatch: remove "ipc" from list of expected toplevel directories
Date: Fri,  8 Nov 2019 17:04:28 +0100	[thread overview]
Message-ID: <20191108160428.9632-1-ggherdovich@suse.cz> (raw)

checkpatch.pl uses a list of expected directory names to understand if it's
being run from the top of a kernel tree. Commit 76128326f97c ("toplevel:
Move ipc/ to kernel/ipc/: move the files") removed a toplevel directory, so
checkpatch.pl need to update its list.

Signed-off-by: Giovanni Gherdovich <ggherdovich@suse.cz>
---
 scripts/checkpatch.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 6fcc66afb088..93b8fd1eea57 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -1099,7 +1099,7 @@ sub top_of_kernel_tree {
 	my @tree_check = (
 		"COPYING", "CREDITS", "Kbuild", "MAINTAINERS", "Makefile",
 		"README", "Documentation", "arch", "include", "drivers",
-		"fs", "init", "ipc", "kernel", "lib", "scripts",
+		"fs", "init", "kernel", "lib", "scripts",
 	);
 
 	foreach my $check (@tree_check) {
-- 
2.16.4


             reply	other threads:[~2019-11-08 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 16:04 Giovanni Gherdovich [this message]
2019-11-08 16:27 ` [PATCH] checkpatch: remove "ipc" from list of expected toplevel directories Giovanni Gherdovich

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=20191108160428.9632-1-ggherdovich@suse.cz \
    --to=ggherdovich@suse.cz \
    --cc=akpm@linux-foundation.org \
    --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).