From: Borislav Petkov <bp@alien8.de>
To: Joe Perches <joe@perches.com>
Cc: Michal Marek <mmarek@suse.cz>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] scripts: add checkmaintainers.py
Date: Tue, 18 Dec 2012 21:47:16 +0100 [thread overview]
Message-ID: <20121218204716.GJ31255@liondog.tnic> (raw)
In-Reply-To: <1355862997.30366.36.camel@joe-AO722>
On Tue, Dec 18, 2012 at 12:36:37PM -0800, Joe Perches wrote:
> You renamed README which is one of the filenames used
> when checkpatch verifies the top-level dir kernel tree.
>
> Don't do that, README is a required filename.
$ git mv scripts/checkpatch{,-2}.pl
$ git diff --cached HEAD -- | ./scripts/checkpatch-2.pl --strict -
ERROR: Does not appear to be a unified-diff format patch
total: 1 errors, 0 warnings, 0 checks, 0 lines checked
Your patch has style problems, please review.
If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
[ adjust .git/hooks/pre-commit to use the new ./scripts/checkpatch-2.pl script
name]
$ git commit -a
scripts/checkpatch-2.pl:2685: space before tab in indent.
+ $ok = 1;
scripts/checkpatch-2.pl:2691: space before tab in indent.
+ $ok = 1;
No joy :(
Let's try another file:
$ git mv arch/x86/Kconfig{,.old}
$ git diff --cached HEAD -- | ./scripts/checkpatch.pl --strict -
ERROR: Does not appear to be a unified-diff format patch
total: 1 errors, 0 warnings, 0 checks, 0 lines checked
Your patch has style problems, please review.
If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
$ git commit -a
arch/x86/Kconfig.old:451: trailing whitespace.
+ Internet Device(MID) platform.
Oh well, enough games for today.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2012-12-18 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:19 Cesar Eduardo Barros
2012-12-17 10:14 ` Michal Marek
2012-12-17 10:27 ` Borislav Petkov
2012-12-17 15:35 ` Joe Perches
2012-12-17 17:00 ` Borislav Petkov
2012-12-17 18:56 ` Joe Perches
2012-12-17 19:09 ` Joe Perches
2012-12-18 18:28 ` Borislav Petkov
2012-12-18 19:34 ` Joe Perches
2012-12-18 20:31 ` Borislav Petkov
2012-12-18 20:36 ` Joe Perches
2012-12-18 20:47 ` Borislav Petkov [this message]
2012-12-18 21:33 ` Joe Perches
2012-12-19 15:07 ` Borislav Petkov
2012-12-19 17:43 ` Joe Perches
2012-12-20 19:31 ` Borislav Petkov
2012-12-17 21:59 ` Cesar Eduardo Barros
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=20121218204716.GJ31255@liondog.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dhowells@redhat.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®