From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@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 v2] Staging iio: adc: Match parenthesis alignment
Date: Sun, 21 Oct 2018 15:41:33 +0100 [thread overview]
Message-ID: <20181021154133.44cf95ab@archlinux> (raw)
In-Reply-To: <20181018013147.15352-1-marcelo.schmitt1@gmail.com>
On Wed, 17 Oct 2018 22:31:47 -0300
Marcelo Schmitt <marcelo.schmitt1@gmail.com> wrote:
> Change close parenthesis alignment to match respective open parenthesis at
> iio/drivers/staging/iio/adc/ad7606.c line 379.
> This makes the file more compliant with the preferred coding style for the
> linux kernel.
Hi Marcelo,
Nice cleanup and applied to the togreg branch of iio.git and pushed
out as testing for the autobuilders to play with it.
(basically this lets 0-day run a whole bunch of build tests on
it before I push it out in a form that others can rely on not changing)
Patch naming is one of those things that is very inconsistent
in different areas of the kernel. I take the view that if I'm going
to be fussy I'll fix it up myself when applying if that is the only
thing I'm otherwise going to comment on.
However, definite preference for the name of the driver being in there
somewhere! When I saw this description I thought we were looking
at a cleanup of the whole directory rather than the single driver
you have here.
Thanks,
Jonathan
>
> Signed-of-by: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
> ---
> drivers/staging/iio/adc/ad7606.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/adc/ad7606.c b/drivers/staging/iio/adc/ad7606.c
> index 0b728b6ea135..230faae38c12 100644
> --- a/drivers/staging/iio/adc/ad7606.c
> +++ b/drivers/staging/iio/adc/ad7606.c
> @@ -376,7 +376,7 @@ static int ad7606_request_gpios(struct ad7606_state *st)
> return 0;
>
> st->gpio_os = devm_gpiod_get_array_optional(dev, "oversampling-ratio",
> - GPIOD_OUT_LOW);
> + GPIOD_OUT_LOW);
> return PTR_ERR_OR_ZERO(st->gpio_os);
> }
>
prev parent reply other threads:[~2018-10-21 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 1:31 [PATCH v2] Staging iio: adc: Match parenthesis alignment Marcelo Schmitt
2018-10-21 14:41 ` 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=20181021154133.44cf95ab@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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=marcelo.schmitt1@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).