From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt@analog.com>
Cc: <apw@canonical.com>, <joe@perches.com>, <dwaipayanray1@gmail.com>,
<lukas.bulwahn@gmail.com>, <paul.cercueil@analog.com>,
<Michael.Hennerich@analog.com>, <lars@metafoo.de>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <dan.carpenter@linaro.org>,
<dlechner@baylibre.com>, <marcelo.schmitt1@gmail.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 11/11] MAINTAINERS: Add MAINTAINERS entry for AD7091R
Date: Thu, 21 Dec 2023 16:59:47 +0000 [thread overview]
Message-ID: <20231221165947.6c64b2c5@jic23-huawei> (raw)
In-Reply-To: <4247e653354f8eb362264189db24c612d5e4e131.1703013352.git.marcelo.schmitt1@gmail.com>
On Tue, 19 Dec 2023 17:32:59 -0300
Marcelo Schmitt <marcelo.schmitt@analog.com> wrote:
> The driver for AD7091R was added in
> ca693001: iio: adc: Add support for AD7091R5 ADC
> but no MAINTAINERS file entry was added for it since then.
> Add a proper MAINTAINERS file entry for the AD7091R driver.
>
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
Hi Marcelo
The series looks good to me now. However timing is a bit against
us because I won't squeeze in another pull request (unless the
kernel release is delayed for some and Linus strong hints at that
this weekend).
What I'll probably do with this series is pull out the first 2 patches
as fixes to go in either at the back end of the merge window or just
after, then pick the rest of the patches up for 6.9.
If I seem to have lost track of them in about the 2nd week of January,
feel free to poke me.
Jonathan
> ---
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4eddc4212f2b..3473cfbac826 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1126,6 +1126,14 @@ F: Documentation/ABI/testing/sysfs-bus-iio-adc-ad4130
> F: Documentation/devicetree/bindings/iio/adc/adi,ad4130.yaml
> F: drivers/iio/adc/ad4130.c
>
> +ANALOG DEVICES INC AD7091R DRIVER
> +M: Marcelo Schmitt <marcelo.schmitt@analog.com>
> +L: linux-iio@vger.kernel.org
> +S: Supported
> +W: http://ez.analog.com/community/linux-device-drivers
> +F: Documentation/devicetree/bindings/iio/adc/adi,ad7091r*
> +F: drivers/iio/adc/drivers/iio/adc/ad7091r*
> +
> ANALOG DEVICES INC AD7192 DRIVER
> M: Alexandru Tachici <alexandru.tachici@analog.com>
> L: linux-iio@vger.kernel.org
next prev parent reply other threads:[~2023-12-21 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 20:25 [PATCH v5 00/11] Add support for AD7091R-2/-4/-8 Marcelo Schmitt
2023-12-19 20:26 ` [PATCH v5 01/11] iio: adc: ad7091r: Allow users to configure device events Marcelo Schmitt
2023-12-19 20:26 ` [PATCH v5 02/11] iio: adc: ad7091r: Enable internal vref if external vref is not supplied Marcelo Schmitt
2023-12-19 20:27 ` [PATCH v5 03/11] iio: adc: ad7091r: Move generic AD7091R code to base driver and header file Marcelo Schmitt
2023-12-19 20:27 ` [PATCH v5 04/11] iio: adc: ad7091r: Move chip init data to container struct Marcelo Schmitt
2023-12-19 20:28 ` [PATCH v5 05/11] iio: adc: ad7091r: Remove unneeded probe parameters Marcelo Schmitt
2023-12-19 20:28 ` [PATCH v5 06/11] iio: adc: ad7091r: Set device mode through chip_info callback Marcelo Schmitt
2023-12-19 20:29 ` [PATCH v5 07/11] iio: adc: ad7091r: Add chip_info callback to get conversion result channel Marcelo Schmitt
2023-12-19 20:29 ` [PATCH v5 08/11] iio: adc: Split AD7091R-5 config symbol Marcelo Schmitt
2023-12-19 20:32 ` [PATCH v5 09/11] dt-bindings: iio: Add AD7091R-8 Marcelo Schmitt
2023-12-19 20:32 ` [PATCH v5 10/11] iio: adc: Add support for AD7091R-8 Marcelo Schmitt
2023-12-19 20:32 ` [PATCH v5 11/11] MAINTAINERS: Add MAINTAINERS entry for AD7091R Marcelo Schmitt
2023-12-21 16:59 ` Jonathan Cameron [this message]
2023-12-22 12:49 ` Marcelo Schmitt
2023-12-26 15:45 ` Jonathan Cameron
2023-12-21 16:53 ` [PATCH v5 00/11] Add support for AD7091R-2/-4/-8 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=20231221165947.6c64b2c5@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=apw@canonical.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=paul.cercueil@analog.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).