From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/2] docs: iio: update dated triggered buffer example
Date: Mon, 18 May 2026 16:33:31 +0100 [thread overview]
Message-ID: <20260518163331.2ba650eb@jic23-huawei> (raw)
In-Reply-To: <20260517-iio-doc-triggered-buffer-update-helpers-v1-0-7f00d4188f6f@baylibre.com>
On Sun, 17 May 2026 12:00:57 -0500
David Lechner <dlechner@baylibre.com> wrote:
> Noticed this example was out of date while grepping for something else.
> And when I did get_maintainer.pl on it, it didn't match the IIO
> subsystem, so we get a bonus patch to fix that too.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
> David Lechner (2):
> MAINTAINERS: add match for IIO API docs
Well I suppose we 'should' maintain those :)
> docs: iio: triggered-buffers: use new helpers in example
Series applied.
Thanks,
Jonathan
>
> Documentation/driver-api/iio/triggered-buffers.rst | 8 ++++----
> MAINTAINERS | 1 +
> 2 files changed, 5 insertions(+), 4 deletions(-)
> ---
> base-commit: 8678fb54958893818ddeccd05fea560a4e1fc759
> change-id: 20260517-iio-doc-triggered-buffer-update-helpers-ef7e3895c9f4
>
> Best regards,
> --
> David Lechner <dlechner@baylibre.com>
>
prev parent reply other threads:[~2026-05-18 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 17:00 [PATCH 0/2] docs: iio: update dated triggered buffer example David Lechner
2026-05-17 17:00 ` [PATCH 1/2] MAINTAINERS: add match for IIO API docs David Lechner
2026-05-17 17:55 ` Stepan Ionichev
2026-05-17 17:00 ` [PATCH 2/2] docs: iio: triggered-buffers: use new helpers in example David Lechner
2026-05-17 17:56 ` Stepan Ionichev
2026-05-18 15:33 ` 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=20260518163331.2ba650eb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--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