From: Jonathan Cameron <jic23@kernel.org>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: Colin Ian King <colin.i.king@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Cosmin Tanislav <cosmin.tanislav@analog.com>,
linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] iio: accel: adxl367: Remove second semicolon
Date: Sat, 16 Mar 2024 14:06:16 +0000 [thread overview]
Message-ID: <20240316140616.09301073@jic23-huawei> (raw)
In-Reply-To: <717ad48efa7ffc6cc1960be05558e9cbf0b6c4c8.camel@gmail.com>
On Fri, 15 Mar 2024 12:51:07 +0100
Nuno Sá <noname.nuno@gmail.com> wrote:
> On Fri, 2024-03-15 at 09:14 +0000, Colin Ian King wrote:
> > There is a statement with two semicolons. Remove the second one, it
> > is redundant.
> >
> > Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> > ---
>
> Reviewed-by: Nuno Sa <nuno.sa@analog.com>
Thanks Colin.
oops.
Applied to the togreg-normal branch of iio.git, but note I'll not rush
this in, so will be the 6.10 merge window now.
Jonathan
>
> > drivers/iio/accel/adxl367.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/accel/adxl367.c b/drivers/iio/accel/adxl367.c
> > index 210228affb80..5cf4828a5eb5 100644
> > --- a/drivers/iio/accel/adxl367.c
> > +++ b/drivers/iio/accel/adxl367.c
> > @@ -621,7 +621,7 @@ static int _adxl367_set_odr(struct adxl367_state *st, enum
> > adxl367_odr odr)
> > static int adxl367_set_odr(struct iio_dev *indio_dev, enum adxl367_odr odr)
> > {
> > iio_device_claim_direct_scoped(return -EBUSY, indio_dev) {
> > - struct adxl367_state *st = iio_priv(indio_dev);;
> > + struct adxl367_state *st = iio_priv(indio_dev);
> > int ret;
> >
> > guard(mutex)(&st->lock);
>
prev parent reply other threads:[~2024-03-16 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 9:14 [PATCH][next] iio: accel: adxl367: Remove second semicolon Colin Ian King
2024-03-15 11:51 ` Nuno Sá
2024-03-16 14:06 ` 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=20240316140616.09301073@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=colin.i.king@gmail.com \
--cc=cosmin.tanislav@analog.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noname.nuno@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 read-only IMAP folder(s) and NNTP newsgroup(s).