From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com
Subject: [Qemu-devel] [PATCH] checkpatch: fix break by renaming README
Date: Thu, 21 Jul 2016 18:15:54 +0800 [thread overview]
Message-ID: <1469096154-16085-1-git-send-email-peterx@redhat.com> (raw)
Without this, we cannot run checkpatch.pl under QEMU root directory.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index afa7f79..8247305 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -286,7 +286,7 @@ sub top_of_kernel_tree {
my @tree_check = (
"COPYING", "MAINTAINERS", "Makefile",
- "README", "docs", "VERSION",
+ "README.md", "docs", "VERSION",
"vl.c"
);
--
2.4.11
next reply other threads:[~2016-07-21 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 10:15 Peter Xu [this message]
2016-07-21 14:37 ` [Qemu-devel] [PATCH] checkpatch: fix break by renaming README Eric Blake
2016-07-22 3:26 ` Peter Xu
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=1469096154-16085-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=qemu-devel@nongnu.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).