From: Nicolas Palix <npalix@diku.dk>
To: Michal Marek <mmarek@suse.cz>
Cc: Kulikov Vasiliy <segooon@gmail.com>,
Kernel Janitors <kernel-janitors@vger.kernel.org>,
Julia Lawall <julia@diku.dk>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Sam Ravnborg <sam@ravnborg.org>,
Joerg Roedel <joerg.roedel@amd.com>,
cocci@diku.dk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coccicheck: use $KBUILD_EXTMOD when available
Date: Wed, 07 Jul 2010 12:22:56 +0000 [thread overview]
Message-ID: <201007071422.56919.npalix@diku.dk> (raw)
In-Reply-To: <4C345F44.4070800@suse.cz>
Hi,
On Wednesday 07 July 2010 13:04:36 Michal Marek wrote:
> On 3.7.2010 21:49, Nicolas Palix wrote:
> > Hi,
> >
> > On Saturday 03 July 2010 17:20:34 Kulikov Vasiliy wrote:
> >> Use $KBUILD_EXTMOD instead of $srctree when the latter is not null
> >> to use make M=somedir.
> >>
> >> Signed-off-by: Kulikov Vasiliy <segooon@gmail.com>
> >> ---
> >> scripts/coccicheck | 8 +++++++-
> >> 1 files changed, 7 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/scripts/coccicheck b/scripts/coccicheck
> >> index b8bcf1f..7d66a55 100755
> >> --- a/scripts/coccicheck
> >> +++ b/scripts/coccicheck
> >> @@ -1,5 +1,11 @@
> >> #!/bin/sh
> >>
> >> +if [ -n "$KBUILD_EXTMOD" ]; then
> >> + CHECK_DIR="$KBUILD_EXTMOD"
> >> +else
> >> + CHECK_DIR="$srctree"
> >> +fi
> >> +
> >> SPATCH="`which ${SPATCH:=spatch}`"
> >>
> >> if [ "$C" = "1" -o "$C" = "2" ]; then
> >> @@ -64,7 +70,7 @@ coccinelle () {
> >> echo ' http://coccinelle.lip6.fr/'
> >> echo ''
> >>
> >> - $SPATCH -D $MODE $FLAGS -sp_file $COCCI $OPT -dir $srctree || exit 1
> >> + $SPATCH -D $MODE $FLAGS -sp_file $COCCI $OPT -dir $CHECK_DIR || exit 1
> >> else
> >> $SPATCH -D $MODE $FLAGS -sp_file $COCCI $OPT $OPTIONS || exit 1
> >> fi
> >>
> >
> > In doing so, the output of the patch mode will produce patches relative to $KBUILD_EXTMOD.
> > I am not sure of what most of developers want but if the patches must be relative to
> > the Linux kernel root, the following patch must be used.
>
> If you are checking your out-of-tree module, then you're probably not
> going to send the resulting patch to lkml.
>
Indeed. I thus acked the original patch last Monday [1].
Thanks.
[1] http://lkml.org/lkml/2010/7/5/136
> Michal
>
--
Nicolas Palix
Tel: (+33) 1 44 27 87 25
Tel: (+33) 6 81 07 91 72
Web: http://www.diku.dk/~npalix/
next prev parent reply other threads:[~2010-07-07 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 15:20 [PATCH] coccicheck: use $KBUILD_EXTMOD when available Kulikov Vasiliy
2010-07-03 19:49 ` Nicolas Palix
2010-07-04 8:41 ` Kulikov Vasiliy
2010-07-07 11:04 ` Michal Marek
2010-07-07 12:22 ` Nicolas Palix [this message]
2010-07-05 12:48 ` Nicolas Palix
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=201007071422.56919.npalix@diku.dk \
--to=npalix@diku.dk \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@diku.dk \
--cc=joerg.roedel@amd.com \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=segooon@gmail.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