From: Jonathan Cameron <jic23@kernel.org>
To: Steven Davis <goldside000@outlook.com>
Cc: hridesh699@gmail.com, Michael.Hennerich@analog.com,
gregkh@linuxfoundation.org, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: iio: Fix alignment warning
Date: Sat, 28 Sep 2024 16:21:46 +0100 [thread overview]
Message-ID: <20240928162146.64251df8@jic23-huawei> (raw)
In-Reply-To: <SJ2P223MB102630DA926C5006D12E5132F7622@SJ2P223MB1026.NAMP223.PROD.OUTLOOK.COM>
On Wed, 18 Sep 2024 15:42:56 -0400
Steven Davis <goldside000@outlook.com> wrote:
> On Wed, 18 Sep 2024 at 23:13:19 +0530, Hridesh MG wrote:
> > Reported by checkpatch:
> >
> > CHECK: Alignment should match open parenthesis
> >
> > Signed-off-by: Hridesh MG <hridesh699@gmail.com>
> Acked-by: Steven Davis <goldside000@outlook.com>
Applied.
Thanks,
Jonathan
> > ---
> > drivers/staging/iio/impedance-analyzer/ad5933.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
>
> > diff --git a/drivers/staging/iio/impedance-analyzer/ad5933.c b/drivers/staging/iio/impedance-analyzer/ad5933.c
> > index 4ae1a7039418..d5544fc2fe98 100644
> > --- a/drivers/staging/iio/impedance-analyzer/ad5933.c
> > +++ b/drivers/staging/iio/impedance-analyzer/ad5933.c
> > @@ -628,9 +628,9 @@ static void ad5933_work(struct work_struct *work)
> > int scan_count = bitmap_weight(indio_dev->active_scan_mask,
> > iio_get_masklength(indio_dev));
> > ret = ad5933_i2c_read(st->client,
> > - test_bit(1, indio_dev->active_scan_mask) ?
> > - AD5933_REG_REAL_DATA : AD5933_REG_IMAG_DATA,
> > - scan_count * 2, (u8 *)buf);
> > + test_bit(1, indio_dev->active_scan_mask) ?
> > + AD5933_REG_REAL_DATA : AD5933_REG_IMAG_DATA,
> > + scan_count * 2, (u8 *)buf);
> > if (ret)
> > return;
> >
> > --
> > 2.46.0
prev parent reply other threads:[~2024-09-28 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 17:43 [PATCH] staging: iio: Fix alignment warning Hridesh MG
2024-09-18 19:42 ` Steven Davis
2024-09-28 15:21 ` 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=20240928162146.64251df8@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=goldside000@outlook.com \
--cc=gregkh@linuxfoundation.org \
--cc=hridesh699@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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