From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Lukas Bulwahn" <lbulwahn@redhat.com>,
"Radu Sabau" <radu.sabau@analog.com>,
linux-iio@vger.kernel.org, "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lukas Bulwahn" <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in ANALOG DEVICES INC AD4691 DRIVER
Date: Mon, 18 May 2026 16:27:30 +0100 [thread overview]
Message-ID: <20260518162730.7bacf931@jic23-huawei> (raw)
In-Reply-To: <CALoEA-yikL+PRDys2tXY5GKZhZtWRYdfhsczrgUWrr+rrbZqBQ@mail.gmail.com>
On Mon, 18 May 2026 14:50:55 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> On Mon, 18 May 2026 at 13:45, Lukas Bulwahn <lbulwahn@redhat.com> wrote:
> >
> > From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> >
> > Commit 963d07535e77 ("docs: iio: adc: ad4691: add driver documentation")
> > adds a file entry in the MAINTAINERS section ANALOG DEVICES INC AD4691
> > DRIVER referring to the non-existing file drivers/iio/adc/ad4691.rst. This
> > commit however adds Documentation/iio/ad4691.rst; so likely, the file entry
> > intends to refer to that newly added file.
> >
> > Correct the file entry to refer to the intended file.
> >
> > Fixes: 963d07535e77 ("docs: iio: adc: ad4691: add driver documentation")
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> > ---
>
> Reviewed-by: Joshua Crofts <joshua.crofts1@gmail.com>
>
Applied.
Thanks,
Jonathan
prev parent reply other threads:[~2026-05-18 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 11:45 Lukas Bulwahn
2026-05-18 12:50 ` Joshua Crofts
2026-05-18 15:27 ` 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=20260518162730.7bacf931@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=lbulwahn@redhat.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=nuno.sa@analog.com \
--cc=radu.sabau@analog.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
all inboxes | Powered by JetHome®