From: Trevor Gamblin <tgamblin@baylibre.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"David Lechner" <dlechner@baylibre.com>,
"Uwe Kleine-Konig" <u.kleine-koenig@baylibre.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v5 3/3] docs: iio: new docs for ad7625 driver
Date: Wed, 16 Oct 2024 09:23:44 -0400 [thread overview]
Message-ID: <ccd95fb3-1756-4d52-bb7b-881502f7ac81@baylibre.com> (raw)
In-Reply-To: <20241015190034.3a6f6761@jic23-huawei>
On 2024-10-15 14:00, Jonathan Cameron wrote:
> On Mon, 09 Sep 2024 10:30:49 -0400
> Trevor Gamblin <tgamblin@baylibre.com> wrote:
>
>> Add documentation for the AD7625/AD7626/AD7960/AD7961 ADCs.
>>
>> Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
> Bot picked up that this wasn't added to index.rst. I fixed up.
Thank you!
>
> Thanks,
>
> Jonathan
next prev parent reply other threads:[~2024-10-16 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 14:30 [PATCH v5 0/3] iio: adc: add new ad7625 driver Trevor Gamblin
2024-09-09 14:30 ` [PATCH v5 1/3] dt-bindings: iio: adc: add AD762x/AD796x ADCs Trevor Gamblin
2024-09-09 14:30 ` [PATCH v5 2/3] iio: adc: ad7625: add driver Trevor Gamblin
2024-10-14 18:33 ` Jonathan Cameron
2024-09-09 14:30 ` [PATCH v5 3/3] docs: iio: new docs for ad7625 driver Trevor Gamblin
2024-10-15 18:00 ` Jonathan Cameron
2024-10-16 13:23 ` Trevor Gamblin [this message]
2024-09-14 17:28 ` [PATCH v5 0/3] iio: adc: add new " Jonathan Cameron
2024-09-16 11:52 ` Uwe Kleine-König
2024-10-12 12:40 ` Jonathan Cameron
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=ccd95fb3-1756-4d52-bb7b-881502f7ac81@baylibre.com \
--to=tgamblin@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.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