From: Jonathan Cameron <jic23@kernel.org>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"raveendra.padasalagi@broadcom.com"
<raveendra.padasalagi@broadcom.com>
Subject: Re: [PATCH] iio: adc: bcm_iproc_adc: drop a stray semicolon
Date: Sat, 9 Nov 2019 12:17:10 +0000 [thread overview]
Message-ID: <20191109121710.7389b110@archlinux> (raw)
In-Reply-To: <5f786ddb2265a0a11a046ab2750ca471f0fc893e.camel@analog.com>
On Mon, 4 Nov 2019 15:15:30 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> On Sun, 2019-10-13 at 13:18 +0100, jic23@kernel.org wrote:
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > Found by coccinelle / coccicheck
> >
> > CHECK drivers/iio/adc/bcm_iproc_adc.c
> > drivers/iio/adc/bcm_iproc_adc.c:311:3-4: Unneeded semicolon
> >
>
> Reviewed-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Applied thanks.
Jonathan
>
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Cc: Raveendra Padasalagi <raveendra.padasalagi@broadcom.com>
> > ---
> > drivers/iio/adc/bcm_iproc_adc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/adc/bcm_iproc_adc.c
> > b/drivers/iio/adc/bcm_iproc_adc.c
> > index 646ebdc0a8b4..5e396104ac86 100644
> > --- a/drivers/iio/adc/bcm_iproc_adc.c
> > +++ b/drivers/iio/adc/bcm_iproc_adc.c
> > @@ -308,7 +308,7 @@ static int iproc_adc_do_read(struct iio_dev
> > *indio_dev,
> > "IntMask set failed. Read will likely
> > fail.");
> > read_len = -EIO;
> > goto adc_err;
> > - };
> > + }
> > }
> > regmap_read(adc_priv->regmap, IPROC_INTERRUPT_MASK, &val_check);
> >
prev parent reply other threads:[~2019-11-09 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 12:18 [PATCH] iio: adc: bcm_iproc_adc: drop a stray semicolon jic23
2019-11-04 15:15 ` Ardelean, Alexandru
2019-11-09 12:17 ` Jonathan Cameron [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=20191109121710.7389b110@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandru.Ardelean@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=raveendra.padasalagi@broadcom.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