public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Julia.Lawall@lip6.fr, nicolas.palix@imag.fr,
	Gilles.Muller@lip6.fr, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, markivx@codeaurora.org,
	stephen.boyd@linaro.org, zohar@linux.vnet.ibm.com,
	broonie@kernel.org, ming.lei@canonical.com, tiwai@suse.d,
	johannes@sipsolutions.net, chunkeey@googlemail.com,
	hauke@hauke-m.de, jwboyer@fedoraproject.org,
	dmitry.torokhov@gmail.com, dwmw2@infradead.org, jslaby@suse.com,
	torvalds@linux-foundation.org, deepa.kernel@gmail.com,
	keescook@chromium.org, cocci@systeme.lip6.fr,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/9] coccicheck: modernize
Date: Fri, 22 Jul 2016 12:14:14 +0200	[thread overview]
Message-ID: <5791F1F6.4040007@suse.com> (raw)
In-Reply-To: <20160713214539.GE6239@wotan.suse.de>

On 2016-07-13 23:45, Luis R. Rodriguez wrote:
> On Wed, Jun 29, 2016 at 03:14:50PM -0700, Luis R. Rodriguez wrote:
>> There were quite a bit of comments from the v3 series [0], since there
>> was quite a bit of review needed for some other changes I've had discussions
>> with Nicolas and Julia privately over these changes and collected their Acks
>> privately to avoid unnecessary e-mail waste.
> 
> *Poke*

Applied to kbuild.git#misc.

Michal

      reply	other threads:[~2016-07-22 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 22:14 [PATCH v4 0/9] coccicheck: modernize Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 1/9] coccicheck: move spatch binary check up Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 2/9] coccicheck: make SPFLAGS more useful Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 3/9] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 4/9] coccicheck: add support for DEBUG_FILE Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 5/9] coccicheck: replace --very-quiet with --quiet when debugging Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 6/9] scripts: add Linux .cocciconfig for coccinelle Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 7/9] coccicheck: add support for requring a coccinelle version Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 8/9] coccicheck: refer to Documentation/coccinelle.txt and wiki Luis R. Rodriguez
2016-06-29 22:14 ` [PATCH v4 9/9] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci Luis R. Rodriguez
2016-07-13 21:45 ` [PATCH v4 0/9] coccicheck: modernize Luis R. Rodriguez
2016-07-22 10:14   ` 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=5791F1F6.4040007@suse.com \
    --to=mmarek@suse.com \
    --cc=Gilles.Muller@lip6.fr \
    --cc=Julia.Lawall@lip6.fr \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=chunkeey@googlemail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=deepa.kernel@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    --cc=jslaby@suse.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markivx@codeaurora.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=nicolas.palix@imag.fr \
    --cc=stephen.boyd@linaro.org \
    --cc=tiwai@suse.d \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.vnet.ibm.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