From: Jonathan Cameron <jic23@kernel.org>
To: Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
antoniu.miclaus@analog.com, lars@metafoo.de,
Michael.Hennerich@analog.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio: adc: ad_sigma_delta: Format block comments
Date: Thu, 26 Mar 2026 08:14:17 +0000 [thread overview]
Message-ID: <20260326081417.6b949211@jic23-huawei> (raw)
In-Reply-To: <CAE7dp2oFaheJMcK_khRRSZnQpAVN8Lgsy_phZsNO=spcbJU+Rg@mail.gmail.com>
On Thu, 26 Mar 2026 12:06:13 +0400
Giorgi Tchankvetadze <giorgitchankvetadze1997@gmail.com> wrote:
> On Thu, Mar 26, 2026 at 12:40 AM Jonathan Cameron <jic23@kernel.org> wrote:
> >
>
> > > I haven’t done a full sweep across iio/adc yet; this was a local fix.
> > > Given how broad this kind of cleanup can get(fixing formatting in
> > > multi line comments in the entire iio/adc directory), I assumed it
> > > would be preferred to keep the scope limited rather than risk missing
> > > cases in a larger series.
> >
> > How big is it looking? I wasn't expecting these to be particularly common.
> >
> > Jonathan
> >
>
> Hi Jonathan,
> I took a closer look.
> There are a handful of similar multi-line comments across
> drivers/iio/adc.. However, a good portion of them
> are file headers, NOTE blocks, or structured comments that appear
> intentional.
>
> There are some cases similar to the one fixed here, but overall it
> doesn’t seem particularly widespread. I think , not widespread enough
> for patch series.
OK. If you want to work on this, send whatever tidy ups look sensible
to you. I don't mind how you break them up into patches / series as
long as finest granularity is one per file. Somewhat coarser is also
fine.
Thanks,
Jonathan
>
>
> Regards,
> Giorgi
prev parent reply other threads:[~2026-03-26 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 11:12 [PATCH v2] iio: adc: ad_sigma_delta: Format block comments Giorgi Tchankvetadze
2026-03-16 10:02 ` Andy Shevchenko
2026-03-21 21:08 ` Jonathan Cameron
2026-03-23 7:20 ` Giorgi Tchankvetadze
2026-03-25 20:40 ` Jonathan Cameron
2026-03-26 8:06 ` Giorgi Tchankvetadze
2026-03-26 8:14 ` 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=20260326081417.6b949211@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=dlechner@baylibre.com \
--cc=giorgitchankvetadze1997@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@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