qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com,
	Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
	stefanha@redhat.com, mst@redhat.com
Subject: [PATCH 2/2] checkpatch: Change occurences of 'kernel' to 'qemu' in user messages
Date: Sat, 20 Jun 2020 15:32:07 +0200	[thread overview]
Message-ID: <20200620133207.26849-3-aleksandar.qemu.devel@gmail.com> (raw)
In-Reply-To: <20200620133207.26849-1-aleksandar.qemu.devel@gmail.com>

It is odd that we inform user that, for example, his current working
directory is not kernel root, when, in face, we mean qemu root.

Replace that and few other similar odd user messages.

Signed-off-by: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
---
 scripts/checkpatch.pl | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index c760c5a4a9..f46c18e413 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -49,7 +49,7 @@ Version: $V
 
 Options:
   -q, --quiet                quiet
-  --no-tree                  run without a kernel tree
+  --no-tree                  run without a qemu tree
   --no-signoff               do not check for 'Signed-off-by' line
   --patch                    treat FILE as patchfile
   --branch                   treat args as GIT revision list
@@ -57,7 +57,7 @@ Options:
   --terse                    one line per report
   -f, --file                 treat FILE as regular source file
   --strict                   fail if only warnings are found
-  --root=PATH                PATH to the kernel tree root
+  --root=PATH                PATH to the qemu tree root
   --no-summary               suppress the per-file summary
   --mailback                 only produce a report in case of warnings/errors
   --summary-file             include the filename in summary
@@ -203,7 +203,7 @@ if ($tree) {
 	}
 
 	if (!defined $root) {
-		print "Must be run from the top-level dir. of a kernel tree\n";
+		print "Must be run from the top-level dir. of a qemu tree\n";
 		exit(2);
 	}
 }
-- 
2.20.1



  parent reply	other threads:[~2020-06-20 13:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 13:32 [PATCH 0/2] checkpatch: Do appropriate kernel->qemu renaming Aleksandar Markovic
2020-06-20 13:32 ` [PATCH 1/2] checkpatch: Rename top_of_kernel_tree() to top_of_qemu_tree() Aleksandar Markovic
2020-06-20 13:32 ` Aleksandar Markovic [this message]
2020-06-20 15:04   ` [PATCH 2/2] checkpatch: Change occurences of 'kernel' to 'qemu' in user messages Peter Maydell
2020-07-01 14:20     ` Paolo Bonzini
2020-07-01 14:26       ` Aleksandar Markovic
2020-07-01 12:57   ` Aleksandar Markovic
2020-06-20 14:25 ` [PATCH 0/2] checkpatch: Do appropriate kernel->qemu renaming Peter Maydell
2020-06-20 15:09   ` Aleksandar Markovic
2020-06-20 15:20     ` Aleksandar Markovic
2020-06-23  8:24       ` Stefan Hajnoczi
2020-06-23  8:26 ` Michael S. Tsirkin

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=20200620133207.26849-3-aleksandar.qemu.devel@gmail.com \
    --to=aleksandar.qemu.devel@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).