From: Ajith Anandhan <ajithanandhan0406@gmail.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] MAINTAINERS: Add entry for TI ADS1120 ADC driver
Date: Fri, 7 Nov 2025 19:13:56 +0530 [thread overview]
Message-ID: <8ab11fa8-defa-47f5-a9cb-e3e95b5b32ca@gmail.com> (raw)
In-Reply-To: <20251030175510.00005af8@huawei.com>
On 10/30/25 11:25 PM, Jonathan Cameron wrote:
> On Thu, 30 Oct 2025 22:04:11 +0530
> Ajith Anandhan <ajithanandhan0406@gmail.com> wrote:
>
>> Add a new MAINTAINERS entry for the Texas Instruments ADS1120
>> ADC driver and its device tree binding.
> blank line before tag block.
Noted.
>> Signed-off-by: Ajith Anandhan <ajithanandhan0406@gmail.com>
> Just bring this in along with the code, it doesn't need a separate
> commit.
>
> Thanks,
>
> Jonathan
I will add along with the code.
>> ---
>> MAINTAINERS | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 3da2c26a7..1efe88fc9 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -25613,6 +25613,13 @@ S: Maintained
>> F: Documentation/devicetree/bindings/iio/adc/ti,ads1119.yaml
>> F: drivers/iio/adc/ti-ads1119.c
>>
>> +TI ADS1120 ADC DRIVER
>> +M: Ajith Anandhan <ajithanandhan0406@gmail.com>
>> +L: linux-iio@vger.kernel.org
>> +S: Maintained
>> +F: Documentation/devicetree/bindings/iio/adc/ti,ads1120.yaml
>> +F: drivers/iio/adc/ti-ads1120.c
>> +
>> TI ADS7924 ADC DRIVER
>> M: Hugo Villeneuve <hvilleneuve@dimonoff.com>
>> L: linux-iio@vger.kernel.org
next prev parent reply other threads:[~2025-11-07 13:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 16:34 [RFC PATCH 0/3] iio: adc: Add support for TI ADS1120 ADC Ajith Anandhan
2025-10-30 16:34 ` [RFC PATCH 1/3] dt-bindings: iio: adc: Add TI ADS1120 binding Ajith Anandhan
2025-10-30 17:12 ` Jonathan Cameron
2025-10-30 20:04 ` David Lechner
2025-11-01 12:24 ` Ajith Anandhan
2025-11-01 11:53 ` Ajith Anandhan
2025-10-30 16:34 ` [RFC PATCH 2/3] iio: adc: Add support for TI ADS1120 Ajith Anandhan
2025-10-30 17:54 ` Jonathan Cameron
2025-11-07 14:40 ` Ajith Anandhan
2025-11-09 14:02 ` Jonathan Cameron
2025-10-30 21:13 ` David Lechner
2025-11-07 15:50 ` Ajith Anandhan
2025-11-07 16:18 ` David Lechner
2025-11-09 8:45 ` Ajith Anandhan
2025-10-30 16:34 ` [RFC PATCH 3/3] MAINTAINERS: Add entry for TI ADS1120 ADC driver Ajith Anandhan
2025-10-30 17:55 ` Jonathan Cameron
2025-11-07 13:43 ` Ajith Anandhan [this message]
2025-10-30 16:40 ` [RFC PATCH 0/3] iio: adc: Add support for TI ADS1120 ADC Krzysztof Kozlowski
[not found] ` <CABPXPSKzOhGicdPLoMFy8xvd0Xx5_D2P2pduteY3QhDRV4d2Ow@mail.gmail.com>
2025-10-30 16:58 ` Ajith Anandhan
2025-10-30 17:08 ` Jonathan Cameron
2025-10-30 19:44 ` Krzysztof Kozlowski
2025-10-31 8:37 ` Andy Shevchenko
2025-11-01 11:37 ` Ajith Anandhan
2025-11-03 7:51 ` Andy Shevchenko
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=8ab11fa8-defa-47f5-a9cb-e3e95b5b32ca@gmail.com \
--to=ajithanandhan0406@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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).