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: Wed, 19 Dec 2012 16:07:32 +0100 [thread overview]
Message-ID: <20121219150732.GD24895@liondog.tnic> (raw)
In-Reply-To: <1355866399.3297.2.camel@joe-AO722>
On Tue, Dec 18, 2012 at 01:33:19PM -0800, Joe Perches wrote:
> On Tue, 2012-12-18 at 21:47 +0100, Borislav Petkov wrote:
> > Oh well, enough games for today.
>
> Maybe try this tomorrow?
$ git diff --cached HEAD -- | ./scripts/checkpatch.pl --strict -
Use of uninitialized value $herecurr in concatenation (.) or string at ./scripts/checkpatch.pl line 1333.
CHECK: Patch renames arch/x86/Kconfig to arch/x86/Kconfig.old, update MAINTAINERS?
yes, except the warning.
$ git commit -a
arch/x86/Kconfig.old:451: trailing whitespace.
+ Internet Device(MID) platform.
This doesn't seem to work although I have the same pre-commit hook as
the above line: " git diff --cached HEAD -- | ./scripts/checkpatch.pl --strict -"
$ git diff --cached HEAD
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig.old
similarity index 100%
rename from arch/x86/Kconfig
rename to arch/x86/Kconfig.old
and this is probably the reason - you said checkpatch needs an unified
diff after the initial lines.
So this is getting closer except checkpatch needs to still warn in the
case where there's no unified diff following *but* a single file rename.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2012-12-19 15:07 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
2012-12-18 21:33 ` Joe Perches
2012-12-19 15:07 ` Borislav Petkov [this message]
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=20121219150732.GD24895@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®