From: Michal Marek <mmarek@suse.cz>
To: Nicolas Palix <nicolas.palix@imag.fr>
Cc: Julia Lawall <julia.lawall@lip6.fr>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Coccicheck: Add the rep+ctxt mode
Date: Thu, 11 Oct 2012 22:15:02 +0200 [thread overview]
Message-ID: <507728C6.9080407@suse.cz> (raw)
In-Reply-To: <CAAxaTiOYpDZTeWbL2UsL-8FJb4rU4RoZaH-gFScU=khY4+44XQ@mail.gmail.com>
Dne 11.10.2012 15:46, Nicolas Palix napsal(a):
> Hi,
>
> On Thu, Oct 11, 2012 at 3:34 PM, Michal Marek <mmarek@suse.cz> wrote:
>> On Thu, Sep 20, 2012 at 10:30:46PM +0200, Nicolas Palix wrote:
>>> This adds a 'rep+ctxt' mode which prints the warning
>>> message followed by the context.
>>>
>>> Signed-off-by: Nicolas Palix <nicolas.palix@imag.fr>
>>> ---
>>> scripts/coccicheck | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/scripts/coccicheck b/scripts/coccicheck
>>> index 823e972..eb43e40 100755
>>> --- a/scripts/coccicheck
>>> +++ b/scripts/coccicheck
>>> @@ -95,6 +95,9 @@ coccinelle () {
>>> $SPATCH -D report $FLAGS -sp_file $COCCI $OPT $OPTIONS -no_show_diff || \
>>> $SPATCH -D context $FLAGS -sp_file $COCCI $OPT $OPTIONS || \
>>> $SPATCH -D org $FLAGS -sp_file $COCCI $OPT $OPTIONS
>>> -no_show_diff || exit 1
>>
>> Your mailer broke this line into two, please try to avoid this next
>> time. Also, please CC lkml when submitting patches. I applied the patch
>> to kbuild.git#misc now.
>
> Ooops.. Sorry. I didn't notice.
>
> The patches are publish on github in my coccicheck branch.
> https://github.com/npalix/linux/commits/coccicheck
>
> Do you prefer a pull request next time to avoid such things ?
Yes, if you base the branch on some tagged release, preferably the
latest -rc1.
Michal
prev parent reply other threads:[~2012-10-11 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAxaTiOsaHOR4cbwcq=xOn-sWxB6PdB4x_UgYf2rUsPQM=WwWA@mail.gmail.com>
2012-10-11 13:15 ` [PATCH 1/3] Coccicheck: Add the rep+ctxt mode Michal Marek
2012-10-11 13:46 ` Nicolas Palix
2012-10-11 20:15 ` Michal Marek [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=507728C6.9080407@suse.cz \
--to=mmarek@suse.cz \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.