From: Joe Perches <joe@perches.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.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 04:08:42 -0700 [thread overview]
Message-ID: <e72efbf7a80cae08041e4ff7be8630044c989c92.camel@perches.com> (raw)
In-Reply-To: <57582495-210b-f9c2-db80-e2ddbc76e7c3@fi.rohmeurope.com>
On Mon, 2022-10-24 at 10:56 +0000, Vaittinen, Matti wrote:
> On 10/24/22 13:40, Joe Perches wrote:
[]
> >
> > 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.
Please do not conflate a "reviewer", someone that "might" look at
a patch and offer comments, and a "supporter", someone that actively
supports the driver/subsystem. I don't have a tree that is pulled
yet I am the get_maintainer and checkpatch maintainer.
next prev parent reply other threads:[~2022-10-24 11:09 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
2022-10-24 11:08 ` Joe Perches [this message]
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=e72efbf7a80cae08041e4ff7be8630044c989c92.camel@perches.com \
--to=joe@perches.com \
--cc=DDRokosov@sberdevices.ru \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jagathjog1996@gmail.com \
--cc=jic23@kernel.org \
--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
Powered by JetHome