From: Jonathan Cameron <jic23@kernel.org>
To: Luciana da Costa Marques <lucianadacostamarques@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-usp@googlegroups.com
Subject: Re: [PATCH v2] iio:accel:adxl345: Change alignment to match paranthesis
Date: Sat, 9 Feb 2019 16:39:31 +0000 [thread overview]
Message-ID: <20190209163931.2005248a@archlinux> (raw)
In-Reply-To: <20190209122542.4872-1-lucianadacostamarques@gmail.com>
On Sat, 9 Feb 2019 10:25:42 -0200
Luciana da Costa Marques <lucianadacostamarques@gmail.com> wrote:
> Align broken line to match upper line parenthesis. Solves the
> checkpatch.pl's message:
>
> CHECK: Alignment should match open parenthesis
>
> Signed-off-by: Luciana da Costa Marques <lucianadacostamarques@gmail.com>
Applied to the togreg branch of iio.git and pushed out as testing
because there are other things in that branch that need checking by
the autobuilders.
Thanks,
Jonathan
> ---
> changes in v2:
> - add full name to commit author
>
> drivers/iio/accel/adxl345_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/accel/adxl345_core.c b/drivers/iio/accel/adxl345_core.c
> index 780f87f72338..f03ed00685ea 100644
> --- a/drivers/iio/accel/adxl345_core.c
> +++ b/drivers/iio/accel/adxl345_core.c
> @@ -150,8 +150,8 @@ static int adxl345_read_raw(struct iio_dev *indio_dev,
> }
>
> static int adxl345_write_raw(struct iio_dev *indio_dev,
> - struct iio_chan_spec const *chan,
> - int val, int val2, long mask)
> + struct iio_chan_spec const *chan,
> + int val, int val2, long mask)
> {
> struct adxl345_data *data = iio_priv(indio_dev);
> s64 n;
prev parent reply other threads:[~2019-02-09 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 12:25 [PATCH v2] iio:accel:adxl345: Change alignment to match paranthesis Luciana da Costa Marques
2019-02-09 16:39 ` 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=20190209163931.2005248a@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=kernel-usp@googlegroups.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucianadacostamarques@gmail.com \
--cc=pmeerw@pmeerw.net \
/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).