* [PATCH] checkpatch: Print filenames of patches
@ 2007-11-18 10:03 Geert Uytterhoeven
2007-11-20 9:11 ` Andy Whitcroft
0 siblings, 1 reply; 2+ messages in thread
From: Geert Uytterhoeven @ 2007-11-18 10:03 UTC (permalink / raw)
To: Andy Whitcroft, Randy Dunlap, Joel Schopp; +Cc: Linux Kernel Development
checkpatch: Print filenames of patches instead of the very uninformative
`Your patch'.
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...
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";
}
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] checkpatch: Print filenames of patches
2007-11-18 10:03 [PATCH] checkpatch: Print filenames of patches Geert Uytterhoeven
@ 2007-11-20 9:11 ` Andy Whitcroft
0 siblings, 0 replies; 2+ messages in thread
From: Andy Whitcroft @ 2007-11-20 9:11 UTC (permalink / raw)
To: Geert Uytterhoeven; +Cc: Randy Dunlap, Joel Schopp, Linux Kernel Development
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-20 9:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-18 10:03 [PATCH] checkpatch: Print filenames of patches Geert Uytterhoeven
2007-11-20 9:11 ` Andy Whitcroft
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox