linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <david@lechnology.com>
Cc: "Julia Lawall" <Julia.Lawall@inria.fr>,
	"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
	"Joe Perches" <joe@perches.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	kernel-janitors@vger.kernel.org,
	"William Breathitt Gray" <vilhelm.gray@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 15/18] counter: use semicolons rather than commas to separate statements
Date: Tue, 29 Sep 2020 16:27:39 +0100	[thread overview]
Message-ID: <20200929162739.40c8257e@archlinux> (raw)
In-Reply-To: <be1d59c5-fd0c-821e-0357-441c26c3d16c@lechnology.com>

On Mon, 28 Sep 2020 10:37:28 -0500
David Lechner <david@lechnology.com> wrote:

> On 9/27/20 2:12 PM, Julia Lawall wrote:
> > Replace commas with semicolons.  What is done is essentially described by
> > the following Coccinelle semantic patch (http://coccinelle.lip6.fr/):
> > 
> > // <smpl>
> > @@ expression e1,e2; @@
> > e1
> > -,
> > +;
> > e2
> > ... when any
> > // </smpl>
> > 
> > Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
> > 
> > ---  
> Reviewed-by: David Lechner <david@lechnology.com>
I've picked this one up.  Applied to the togreg branch of iio.git and
pushed out as testing for all the normal reasons.

Thanks,

Jonathan

> 


  reply	other threads:[~2020-09-29 15:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27 19:12 [PATCH 00/18] use semicolons rather than commas to separate statements Julia Lawall
2020-09-27 19:12 ` [PATCH 15/18] counter: " Julia Lawall
2020-09-28 15:37   ` David Lechner
2020-09-29 15:27     ` Jonathan Cameron [this message]
2020-09-27 20:08 ` [PATCH 00/18] " Joe Perches
     [not found] ` <160132172369.55460.9237357219623604216.b4-ty@kernel.org>
2020-09-29  0:45   ` Joe Perches
2020-09-29 11:37     ` Mark Brown
2020-09-29 11:46       ` Julia Lawall
2020-09-29 12:37         ` Mark Brown
2020-09-29 12:44           ` Julia Lawall
2020-09-30 19:33       ` Joe Perches
2020-10-01 11:01         ` Mark Brown
2020-10-03 18:40           ` Joe Perches
2020-10-03 19:15             ` Konstantin Ryabitsev
2020-10-03 19:18               ` Julia Lawall
2020-10-03 19:31                 ` Konstantin Ryabitsev
2020-10-03 19:43                   ` Joe Perches
2020-10-05 16:52                     ` Mark Brown
2020-10-03 19:27               ` Joe Perches
2020-10-03 19:36                 ` Joe Perches
2020-09-29 12:20 ` Ard Biesheuvel
2020-09-29 12:36   ` Julia Lawall
2020-09-29 12:41   ` Dan Carpenter
2020-09-29 12:47     ` Julia Lawall
2020-09-29 13:34       ` Joe Perches
2020-09-29 13:42         ` Julia Lawall
2020-09-29 13:42         ` Shuah Khan
2020-10-02 16:47           ` Shuah Khan

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=20200929162739.40c8257e@archlinux \
    --to=jic23@kernel.org \
    --cc=Julia.Lawall@inria.fr \
    --cc=david@lechnology.com \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=valdis.kletnieks@vt.edu \
    --cc=vilhelm.gray@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;
as well as URLs for NNTP newsgroup(s).