From: Jonathan Cameron <jic23@kernel.org>
To: "João Seckler" <joaoseckler@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com,
stefan.popa@analog.com, knaack.h@gmx.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
kernel-usp@googlegroups.com
Subject: Re: [PATCH] staging: iio: adt7316: match parenthesis alignment
Date: Sun, 5 May 2019 13:06:34 +0100 [thread overview]
Message-ID: <20190505130634.4bd56579@archlinux> (raw)
In-Reply-To: <20190429175939.2jvt4qwrtbmpvhl6@smtp.gmail.com>
On Mon, 29 Apr 2019 14:59:40 -0300
João Seckler <joaoseckler@gmail.com> wrote:
> This patch solves the following checkpatch.pl message:
> CHECK: Alignment should match open parenthesis.
> This makes the file more compliant with the preferred coding style for
> the Linux kernel.
>
> Signed-off-by: João Seckler <joaoseckler@gmail.com>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
> ---
> drivers/staging/iio/addac/adt7316.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/addac/adt7316.c b/drivers/staging/iio/addac/adt7316.c
> index b6a65ee8d558..37ce563cb0e1 100644
> --- a/drivers/staging/iio/addac/adt7316.c
> +++ b/drivers/staging/iio/addac/adt7316.c
> @@ -2154,7 +2154,7 @@ int adt7316_probe(struct device *dev, struct adt7316_bus *bus,
> chip->dac_bits = 8;
>
> chip->ldac_pin = devm_gpiod_get_optional(dev, "adi,ldac",
> - GPIOD_OUT_LOW);
> + GPIOD_OUT_LOW);
> if (IS_ERR(chip->ldac_pin)) {
> ret = PTR_ERR(chip->ldac_pin);
> dev_err(dev, "Failed to request ldac GPIO: %d\n", ret);
prev parent reply other threads:[~2019-05-05 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 17:59 [PATCH] staging: iio: adt7316: match parenthesis alignment João Seckler
2019-05-05 12: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=20190505130634.4bd56579@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joaoseckler@gmail.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=pmeerw@pmeerw.net \
--cc=stefan.popa@analog.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).