From: Andy Whitcroft <apw@shadowen.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Joel Schopp <jschopp@austin.ibm.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Print filenames of patches
Date: Tue, 20 Nov 2007 09:11:00 +0000 [thread overview]
Message-ID: <20071120091047.GA12066@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711181103070.1009@anakin>
On Sun, Nov 18, 2007 at 11:03:47AM +0100, Geert Uytterhoeven wrote:
> checkpatch: Print filenames of patches instead of the very uninformative
> `Your patch'.
Well this isn't quite enough as we often use this thing checking its
stdin. Which leads to an even less useful '- has no obvious ...'. I
guess a hybrid would be an improvement.
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> This patch is not `checkpatch' clean :-)
> Although I shortened 2 lines, they're still longer than 80 characters...
Heh, yeah its a pig getting those RE's into 80 chars.
> scripts/checkpatch.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -1408,10 +1408,10 @@ sub process {
> }
> }
> if ($clean == 1 && $quiet == 0) {
> - print "Your patch has no obvious style problems and is ready for submission.\n"
> + print "$filename has no obvious style problems and is ready for submission.\n"
> }
> if ($clean == 0 && $quiet == 0) {
> - print "Your patch has style problems, please review. If any of these errors\n";
> + print "$filename has style problems, please review. If any of these errors\n";
> print "are false positives report them to the maintainer, see\n";
> print "CHECKPATCH in MAINTAINERS.\n";
> }
-apw
prev parent reply other threads:[~2007-11-20 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 10:03 [PATCH] checkpatch: Print filenames of patches Geert Uytterhoeven
2007-11-20 9:11 ` Andy Whitcroft [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=20071120091047.GA12066@shadowen.org \
--to=apw@shadowen.org \
--cc=geert@linux-m68k.org \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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