linux-kernel - Re: [PATCH v4 3/3] MAINTAINERS: Add KX022A maintainer entry

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ea05a744-0eb4-a18e-c238-a1e3d99c8aea@fi.rohmeurope.com>
Date:   Mon, 24 Oct 2022 11:36:33 +0000
From:   "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
To:     Joe Perches <joe@...ches.com>,
        Matti Vaittinen <mazziesaccount@...il.com>
CC:     Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Dmitry Rokosov <DDRokosov@...rdevices.ru>,
        Nikita Yushchenko <nikita.yoush@...entembedded.com>,
        Cosmin Tanislav <demonsingur@...il.com>,
        Jagath Jog J <jagathjog1996@...il.com>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 3/3] MAINTAINERS: Add KX022A maintainer entry

On 10/24/22 14:08, Joe Perches wrote:
> 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.

I'd like to ask what the "actively support a driver" means in practice 
as I am pretty sure that is what I do. So perhaps I should change myself 
from a reviewer to a maintainer for these drivers then.

Yours
	-- Matti


-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~