Linux IIO development
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tomas Melin <tomas.melin@vaisala.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Nuno Sa <nuno.sa@analog.com>, Jonathan Cameron <jic23@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/3] iio: adc: ad9467: sort header includes
Date: Tue, 9 Dec 2025 20:17:45 +0200	[thread overview]
Message-ID: <aThnybDs4lk9ht_f@smile.fi.intel.com> (raw)
In-Reply-To: <7a792f4e-edba-42f3-bcc8-76004972c2f7@vaisala.com>

On Tue, Dec 09, 2025 at 05:46:16PM +0200, Tomas Melin wrote:
> On 09/12/2025 16:41, Andy Shevchenko wrote:
> > On Tue, Dec 9, 2025 at 7:34 AM Tomas Melin <tomas.melin@vaisala.com> wrote:
> >>
> >> Include headers in ascending order.
> > 
> > Thanks, but...
> > 
> >>  #include <linux/iio/backend.h>
> >>  #include <linux/iio/iio.h>
> >>  #include <linux/iio/sysfs.h>
> > 
> > ...this was specifically grouped to show the relation to the certain
> > subsystem. At the end we should have something like this
> > 
> > linux/*.h // generic ones
> > ...blank line...
> > asm/*.h // generic ones (optionally, if there is a need in a such)
> > ...blank line...
> > linux/iio/*.h
> > ...blank line...
> 
> Thanks for the clarification. Sure, it's not a big deal to do a new
> version. But FWIW, that convention is not AFAIS explicitly stated
> anywhere and with even recent drivers not all following it, it's
> somewhat hard to know what expected formatting should be.
> It would really be good to have that documented somewhere.

I fully agree. The problem with such a documentation is that you will always
have 50/50% split at best. At worse ~100% will be against any doc updates
like this. For minimum we can do it on an IIO level (only for this subsystem),
see how others do Documentation/process/maintainer-*.rst. There is no IIO.
You can start it :-)

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-12-09 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  5:32 [PATCH v4 0/3] iio: adc: ad9467: add support for ad9211 Tomas Melin
2025-12-09  5:32 ` [PATCH v4 1/3] dt-bindings: " Tomas Melin
2025-12-09  5:32 ` [PATCH v4 2/3] iio: adc: ad9467: sort header includes Tomas Melin
2025-12-09 14:41   ` Andy Shevchenko
2025-12-09 15:46     ` Tomas Melin
2025-12-09 18:17       ` Andy Shevchenko [this message]
2025-12-13 16:34         ` Jonathan Cameron
2025-12-09  5:32 ` [PATCH v4 3/3] iio: adc: ad9467: add support for ad9211 Tomas Melin

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=aThnybDs4lk9ht_f@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=tomas.melin@vaisala.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