From: Andy Whitcroft <apw@canonical.com>
To: Rabin VINCENT <rabin.vincent@stericsson.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus WALLEIJ <linus.walleij@stericsson.com>
Subject: Re: [PATCH] checkpatch: check for incorrect permissions
Date: Wed, 18 Aug 2010 12:10:02 +0100 [thread overview]
Message-ID: <20100818111002.GQ6193@shadowen.org> (raw)
In-Reply-To: <20100813045528.GA32350@bnru01.bnr.st.com>
On Fri, Aug 13, 2010 at 10:25:29AM +0530, Rabin VINCENT wrote:
> On Thu, Aug 12, 2010 at 23:02:22 +0200, Andrew Morton wrote:
> > On Thu, 12 Aug 2010 10:45:45 +0530
> > Rabin Vincent <rabin.vincent@stericsson.com> wrote:
> > > # extract the filename as it passes
> > > - if ($line=~/^\+\+\+\s+(\S+)/) {
> > > + if ($line=~/^\+\+\+\s+(\S+)/ || $line=~/^diff\s.*?(\S+)$/) {
> >
> > Breakage. This causes the false warning:
> >
> > WARNING: patch prefix 'drivers' exists, appears to be a -p0 patch
>
> I've fixed this by matching for the filename in the diff line only when
> it's "diff --git". Also prevented a double-print of the "do not modify
> file in include/asm" error.
>
> From b854ea24f1bd5391a63d8d4e2aa63e1c10870816 Mon Sep 17 00:00:00 2001
> From: Rabin Vincent <rabin.vincent@stericsson.com>
> Date: Wed, 11 Aug 2010 14:45:45 +0530
> Subject: [PATCHv2] checkpatch: check for incorrect permissions
That one looks better. I've pull this updated one (slightly modified)
into my tree.
Andrew, will send you this shortly.
-apw
prev parent reply other threads:[~2010-08-18 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 5:15 [PATCH] checkpatch: check for incorrect permissions Rabin Vincent
2010-08-12 21:02 ` Andrew Morton
2010-08-13 4:55 ` Rabin VINCENT
2010-08-18 11:10 ` 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=20100818111002.GQ6193@shadowen.org \
--to=apw@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin.vincent@stericsson.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