From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: MAINTAINERS: add status for IRQ helpers
Date: Thu, 21 Dec 2023 09:02:40 +0100 [thread overview]
Message-ID: <5397da38-80e9-4e75-806d-0b92b2b5d475@linaro.org> (raw)
In-Reply-To: <cbc4247c-323b-4f4e-8963-fcad7da9528e@gmail.com>
On 21/12/2023 07:17, Matti Vaittinen wrote:
> Hi Krzysztof,
>
> On 12/18/23 12:28, Krzysztof Kozlowski wrote:
>> Each maintainer entry should have a status field:
>>
>> $ ./scripts/get_maintainer.pl --self-test=sections
>> ./MAINTAINERS:23368: warning: section without status
>>
>> Fixes: d55444adedae ("MAINTAINERS: Add reviewer for regulator irq_helpers")
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 30322190a72f..6fd22db830f5 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -23367,6 +23367,7 @@ K: regulator_get_optional
>>
>> VOLTAGE AND CURRENT REGULATOR IRQ HELPERS
>> R: Matti Vaittinen <mazziesaccount@gmail.com>
>> +S: Maintained
>
> Isn't that a bit odd seeing the M: - entry is missing as well?
>
> This entry falls under the drivers/regulator, and as such, is maintained
> by Mark (and the "umbrella" entry VOLTAGE AND CURRENT REGULATOR
> FRAMEWORK has all needed bits and pieces, like the M: and S:).
>
> I think the current MAINTAINERS entries reflect the reality. Mark (and
> Liam) are THE regulator guy(s). I am just doing bits and pieces here and
> there, like reviewing the changes to these helpers.
And your piece needs S: to explain whether you do odd fixes, maintaining
or supporting. Although I understand questioning this with only R:, but
I would argue that it still applies - reviewing odd fixes, reviewing
unpaid or paid.
>
> I guess that from a technical POV duplicating the S: and M: here is a
> bit pointless, and as all duplicates, adds overhead when changes are done.
M: is optional, anyway the M: field from regulators count, but status
can be different than from the parent.
> I am happy with the existing entries, but seems like everyone else is
> not. Still, having S: without M: can be a source of confusion. If S: is
> required, maybe add Mark as M: here as well. (Or if this is not Ok with
> Mark, switch my R to M - which in my opinion is still a bit pointless as
> the changes to drivers/regulator/irq_helpers.c will flow through Mark's
> hands in any case :] )
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-21 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 10:28 Krzysztof Kozlowski
2023-12-21 6:17 ` Matti Vaittinen
2023-12-21 8:02 ` Krzysztof Kozlowski [this message]
2023-12-22 6:57 ` Matti Vaittinen
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=5397da38-80e9-4e75-806d-0b92b2b5d475@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.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®