From: Krzysztof Kozlowski <krzk@kernel.org>
To: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
Cc: alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, skhan@linuxfoundation.org,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, akhileshpatilvnit@gmail.com
Subject: Re: [PATCH v2 1/6] dt-bindings: rtc: Add ST m41t93
Date: Wed, 17 Sep 2025 09:52:24 +0900 [thread overview]
Message-ID: <85a46710-64ee-4a21-b95c-d4c18c2f634f@kernel.org> (raw)
In-Reply-To: <20250915141951.GA3239298@bhairav-test.ee.iitb.ac.in>
On 15/09/2025 16:19, Akhilesh Patil wrote:
>>> +$id: http://devicetree.org/schemas/rtc/st,m41t93.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: ST M41T93 RTC and compatible
>>> +
>>> +maintainers:
>>> + - linux-rtc@vger.kernel.org
>>
>> Not much improved. This should be a person responsible/caring about this
>> hardware support in the kernel. Why would we want to take the binding if
>> no one cares about it?
>
> Okay. As per get_maintainer.pl, linux driver corresponding to this binding does not have a dedicated
> maintainer, hence it shows rtc subsystem maintainer (Alexandre Belloni).
And what did I express at v1?
> Looking forward for your suggestion here.
> What do you suggest to keep maintainer as Rob Herring or/and me ? as I see in
> such cases Rob is the maintainer.
No, I really doubt Rob cares about this particular hardware. Neither do
I, nor Conor.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-17 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 13:52 [PATCH v2 0/6] rtc: m41t93: add new features alarm, clock out, watchdog Akhilesh Patil
2025-09-10 13:52 ` [PATCH v2 1/6] dt-bindings: rtc: Add ST m41t93 Akhilesh Patil
2025-09-11 7:43 ` Krzysztof Kozlowski
2025-09-15 14:19 ` Akhilesh Patil
2025-09-17 0:52 ` Krzysztof Kozlowski [this message]
2025-09-20 14:47 ` Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 2/6] rtc: m41t93: add device tree support Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 3/6] rtc: m41t93: migrate to regmap api for register access Akhilesh Patil
2025-09-10 13:53 ` [PATCH v2 4/6] rtc: m41t93: Add alarm support Akhilesh Patil
2025-09-10 13:54 ` [PATCH v2 5/6] rtc: m41t93: Add square wave clock provider support Akhilesh Patil
2025-09-10 13:54 ` [PATCH v2 6/6] rtc: m41t93: Add watchdog support Akhilesh Patil
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=85a46710-64ee-4a21-b95c-d4c18c2f634f@kernel.org \
--to=krzk@kernel.org \
--cc=akhilesh@ee.iitb.ac.in \
--cc=akhileshpatilvnit@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).