From: Jonathan Cameron <jic23@kernel.org>
To: Angelo Dureghello <adureghello@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Jonathan Corbet" <corbet@lwn.net>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/5] docs: iio: add documentation for ad3552r driver
Date: Sat, 12 Apr 2025 13:55:22 +0100 [thread overview]
Message-ID: <20250412135522.6bc83c52@jic23-huawei> (raw)
In-Reply-To: <20250409-wip-bl-ad3552r-fixes-v5-2-fb429c3a6515@baylibre.com>
On Wed, 09 Apr 2025 20:36:29 +0200
Angelo Dureghello <adureghello@baylibre.com> wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Add documentation for ad3552r driver, needed to describe the high-speed
> driver debugfs attributes and shows how the user may use them.
>
> Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
There is a double blank line at the end of this file that git moaned about.
I fixed it up whilst applying.
next prev parent reply other threads:[~2025-04-12 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 18:36 [PATCH v5 0/5] iio: ad3552r-hs: add support for internal ramp generator Angelo Dureghello
2025-04-09 18:36 ` [PATCH v5 1/5] iio: dac: adi-axi-dac: add cntrl chan check Angelo Dureghello
2025-04-09 18:36 ` [PATCH v5 2/5] docs: iio: add documentation for ad3552r driver Angelo Dureghello
2025-04-12 12:55 ` Jonathan Cameron [this message]
2025-04-09 18:36 ` [PATCH v5 3/5] iio: backend: add support for data source get Angelo Dureghello
2025-04-09 18:36 ` [PATCH v5 4/5] iio: dac: adi-axi-dac: add " Angelo Dureghello
2025-04-09 18:36 ` [PATCH v5 5/5] iio: dac: ad3552r-hs: add support for internal ramp Angelo Dureghello
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=20250412135522.6bc83c52@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=adureghello@baylibre.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--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=olivier.moysan@foss.st.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