From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: Joe Perches <joe@perches.com>,
Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Rokosov <DDRokosov@sberdevices.ru>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
Cosmin Tanislav <demonsingur@gmail.com>,
Jagath Jog J <jagathjog1996@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] MAINTAINERS: Add KX022A maintainer entry
Date: Mon, 24 Oct 2022 10:56:49 +0000 [thread overview]
Message-ID: <57582495-210b-f9c2-db80-e2ddbc76e7c3@fi.rohmeurope.com> (raw)
In-Reply-To: <6b9b7f9d835a271312bd5955d96b83bd14c9e6fa.camel@perches.com>
On 10/24/22 13:40, Joe Perches wrote:
> On Mon, 2022-10-24 at 07:24 +0000, Vaittinen, Matti wrote:
>> Hi Joe,
>>
>> On 10/24/22 09:52, Joe Perches wrote:
>>> On Fri, 2022-10-21 at 14:23 +0300, Matti Vaittinen wrote:
>>>> Add maintainer entry for ROHM/Kionix KX022A accelerometer sensor driver.
>>>>
>>>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>>>> ---
>>>> MAINTAINERS | 5 +++++
>>>> 1 file changed, 5 insertions(+)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index cf0f18502372..3ab9c5f97dfe 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -11435,6 +11435,11 @@ F: drivers/mfd/khadas-mcu.c
>>>> F: include/linux/mfd/khadas-mcu.h
>>>> F: drivers/thermal/khadas_mcu_fan.c
>>>>
>>>> +KIONIX/ROHM KX022A ACCELEROMETER
>>>> +R: Matti Vaittinen <mazziesaccount@gmail.com>
>>>> +S: Supported
>>>> +F: drivers/iio/accel/kionix-kx022a*
>>>
>>> How is this "S: Supported" without an M: maintainer?
>>
>> I am currently paid to work with the Kionix/ROHM upstream drivers. Hence
>> I add 'S:' to ones I am looking after.
>>
>> The ideology why I have 'R' and not 'M' is summarized by my earlier patch:
>>
>> >> I can also add myself as a maintainer instead of a reviewer if it better
>> >> suits iio maintainer. I however don't plan setting up my own public
>> >> repository and hope the further patches will be merged via IIO tree.
>> >>
>> >> So, as Geert once explained to me - In that case the difference between
>> >> me as a maintainer vs. a reviewer would be only really relevant to the
>> >> subsystem (in this case IIO) maintainer. The subsystem maintainer who
>> >> merges patches is allowed to take in changes acked by downstream
>> >> maintainer w/o obligation to do thorough review. (Downstream
>> maintainer is
>> >> to be blamed if things explode :]). If ack is given by a reviewer, then
>> >> the subsystem maintainer has the full responsibility and should always
>> >> do the review. Or - this is how I remember our discussion went - feel
>> >> free to correct me if I am wrong :] In any case - please let me know if
>> >> you'd rather see M: not R: in front of my name for the kx022a.
>>
>> This seemed to be fine with Jonathan:
>>
>> https://lore.kernel.org/all/87ac9a5e-b5ba-82f3-c00c-75d5e6f01597@gmail.com/
>>
>> I've also written a longer version of this in an LinkedIn article:
>> https://www.linkedin.com/pulse/should-you-linux-kernel-maintainer-matti-vaittinen/
>>
>> (I enjoy writing small stories. So doing an occasional small LinkedIn
>> articles on working with the upstream is kind of an hobby for me.)
>>
>> Anyways, I don't see a contradiction with 'S + R' compared to 'S + M'.
>> Well, please educate me if I am wrong :]
>
> The subsystem is one thing, someone outside of KIONIX/ROHM may be
> supporting the subsystem. If this _particular_ driver is "supported"
Yes. I am supporting this particular driver, assuming the support means
ability and willingness to review and even occsionally test some changes
- or to occasionally even discuss with the ASIC designers.
Basically, what I don't do (and what in my head distinguishes me from
"real" maintainers) is hosting the a public git tree.
> there should be an individual listed as its actual maintainer, not
> just a person that might review submitted patches.
I don't think listing me as Maintainer or Reviewer will in practice
change how I am looking after the code. I will get the patches/questions
regarding the driver even if I am listed as a reviewer and not a as a
maintainer, right? Besides, "a person that might review" is not any
worse than "a person that might maintain"... I think there are quite a
few MAINTAINER entries with 'M: <foo@bar>' who are absent these days. I
would not value 'M' over 'R'.
>
> S: *Status*, one of the following:
> Supported: Someone is actually paid to look after this. > Maintained: Someone actually looks after it.
>
> "this" is this particular driver, not any subsystem "above" it.
Yes. And as I wrote, I am paid to look after this driver as well as
other drivers I've submitted upstream for ROHM components (Kionix being
part of ROHM these days). I have used this Supported + Reviewer
combination for all other IC drivers as well. This is why, by
definition, the S eg. supported is correct. Question is whether one
supporting a driver must be a maintainer? If this is the case, then I'd
better review all of my MAINTAINER entries. However, I (still) don't see
the problem of having a reviewer supporting the IC.
Yours
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2022-10-24 10:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:21 [PATCH v4 0/3] iio: Support ROHM/Kionix kx022a Matti Vaittinen
2022-10-21 11:21 ` [PATCH v4 1/3] dt-bindings: iio: Add KX022A accelerometer Matti Vaittinen
2022-10-21 11:22 ` [PATCH v4 2/3] iio: accel: Support Kionix/ROHM " Matti Vaittinen
2022-10-21 12:41 ` Andy Shevchenko
2022-10-21 12:47 ` Matti Vaittinen
2022-10-23 11:43 ` Jonathan Cameron
2022-10-24 5:44 ` Vaittinen, Matti
2022-10-29 11:35 ` Jonathan Cameron
2022-10-31 6:25 ` Vaittinen, Matti
2022-10-24 13:34 ` Christophe JAILLET
2022-10-24 14:16 ` Matti Vaittinen
2022-10-21 11:23 ` [PATCH v4 3/3] MAINTAINERS: Add KX022A maintainer entry Matti Vaittinen
2022-10-24 6:52 ` Joe Perches
2022-10-24 7:24 ` Vaittinen, Matti
2022-10-24 10:40 ` Joe Perches
2022-10-24 10:56 ` Vaittinen, Matti [this message]
2022-10-24 11:08 ` Joe Perches
2022-10-24 11:36 ` Vaittinen, Matti
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=57582495-210b-f9c2-db80-e2ddbc76e7c3@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=DDRokosov@sberdevices.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jagathjog1996@gmail.com \
--cc=jic23@kernel.org \
--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=mazziesaccount@gmail.com \
--cc=nikita.yoush@cogentembedded.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).