From: David Lechner <dlechner@baylibre.com>
To: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>,
antoniu.miclaus@analog.com
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: max1363: Fix leading space indentation
Date: Fri, 6 Mar 2026 08:40:57 -0600 [thread overview]
Message-ID: <8a3f7f55-8d76-476b-9768-5c5a3c4a570e@baylibre.com> (raw)
In-Reply-To: <20260306134332.746728-5-giorgitchankvetadze1997@gmail.com>
On 3/6/26 7:43 AM, Giorgi Tchankvetadze wrote:
> Fix leading space indentation in the device enum (found by checkpatch).
>
> No functional change.
>
> Signed-off-by: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
> ---
> drivers/iio/adc/max1363.c | 74 +++++++++++++++++++--------------------
> 1 file changed, 37 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/iio/adc/max1363.c b/drivers/iio/adc/max1363.c
> index d35f4487b2f9..75af10bc37de 100644
> --- a/drivers/iio/adc/max1363.c
> +++ b/drivers/iio/adc/max1363.c
> @@ -638,43 +638,43 @@ static const struct iio_chan_spec max11646_channels[] = MAX1363_2X_CHANS(10);
> static const struct iio_chan_spec max11644_channels[] = MAX1363_2X_CHANS(12);
>
> enum { max1361,
We should also move max1361 to a new line if we are cleaning this up.
> };
>
> static const int max1363_monitor_speeds[] = { 133000, 665000, 33300, 16600,
And would be nice to move these values to a new line too to keep the style
consistent.
next prev parent reply other threads:[~2026-03-06 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 13:43 Giorgi Tchankvetadze
2026-03-06 14:40 ` Andy Shevchenko
2026-03-06 14:40 ` David Lechner [this message]
2026-03-07 7:21 ` Giorgi Tchankvetadze
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=8a3f7f55-8d76-476b-9768-5c5a3c4a570e@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=giorgitchankvetadze1997@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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
all inboxes | Powered by JetHome®