Linux Documentation
 help / color / mirror / Atom feed
From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: David Lechner <dlechner@baylibre.com>,
	Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Flaviu Nistor <flaviu.nistor@gmail.com>,
	linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: iio: add documentation for ti-ads1015 driver
Date: Mon, 26 Oct 2026 07:51:11 +0200	[thread overview]
Message-ID: <20261026055111.4572-1-flaviu.nistor@gmail.com> (raw)
In-Reply-To: <20261021202210.7d70429b@jic23-hlaptop>

On Wed, Oct 21, 2026 at 10:22 PM, Jonathan Cameron wrote:
>On Wed, 21 Oct 2026 09:33:50 +0300
>Flaviu Nistor <flaviu.nistor@gmail.com> wrote:
>
>> Add documentation for the ADS1015 ADC IIO driver, which describes channels,
>> IIO attributes, threshold events and ABI usage examples.
>> 
>Hi Flaviu
>This is missing the 'why'?
>

Hello Jonathan,

the "why" seems to be a misunderstanding on my side. I had the impression that is it a
good practice (even expected) that each driver also has a documentation (as I see a much
higher driver doc coverage in hwmon subsystem for example). When I have send a patch for
this driver adding label support I observed that it has no documentation.
Now is clear that this is no the case (at least for IIO subsystem), so please ignore
this patch. Sorry for the noise.

Best regards,
Flaviu

>We don't tend to add per driver documentation unless there are some
>oddities or unique aspects that aren't described by more generic
>documentation.  The actual features are all discoverable so documenting
>those rarely makes sense.
>
>If you have a reason that it makes sense to document this specific
>driver then state that clearly in this patch description.
>
>Thanks,
>Jonathan
>
>
> Signed-off-by: Flaviu Nistor <flaviu.nistor@gmail.com>

      reply	other threads:[~2026-10-26  5:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  6:33 [PATCH] docs: iio: add documentation for ti-ads1015 driver Flaviu Nistor
2026-10-21 19:22 ` Jonathan Cameron
2026-10-26  5:51   ` Flaviu Nistor [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=20261026055111.4572-1-flaviu.nistor@gmail.com \
    --to=flaviu.nistor@gmail.com \
    --cc=andy@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=skhan@linuxfoundation.org \
    /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