Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp6626998rwi; Mon, 24 Oct 2022 04:11:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6mLu+kZfjusAJkr/E1HGrx1XsaS7mjn8/o/edUfB4kR8yQBLlaFXBfcNB43r6k9tjJ7l/o X-Received: by 2002:a05:6a02:10a:b0:461:26b8:1c95 with SMTP id bg10-20020a056a02010a00b0046126b81c95mr26289739pgb.503.1666609887256; Mon, 24 Oct 2022 04:11:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666609887; cv=none; d=google.com; s=arc-20160816; b=t4qKoyiP28B07d8WjWrurhe8FryAe0ACZkp5GSQ621jK528ASJoiWh9NCK6XxbrMqz 39L/m7SPLtcPv0HDDH1+MKZsq4UWcyCln6oks4PEe1bCln22Z34Hm8rs2zxhtozzesrT Gr309x+VMCExHsS6TYDGVm4kZ17vZ1JSnbRIu0Chdg2GJmQ6+Xy97dBiLrt34qlA/EdY jPRaDfc2cKzUICOc8BXc5VPJp/qruITl1yuGc68h9yamBDJuBxtd3rm/BEJVK58/0PfR VsFeypbQ7nhYbDvxTEn0s4LxlKYZjVmNliHwN4YMEmvrRfNTzu1eUrsRDaEegBa6BPYP wkZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id; bh=qDO9dvjFYhqXxXawHXW2VclImVcmFlLrbZu9WELrh7s=; b=ujA/E457QTgonQjYuSRBPouxZIwwcRXPYn52iHNKzQJ0lwrR6Dhc9Wfj7cx6HJB4PG yRgKTzhBFVgyYYYpP9ou51uH+DpsYeCFTwXsZ5RtNTQyoZQZwYSuBhjONCIxA9zlI1WZ JTH4mydlV8xsPF0SjRHrzq6BWkYGP7VP+5wqIOa6I9i2idTob9QHsv3r9FWMuUaU24ni 0MBv+56AAfnpz4zwAIZ7PXzVAB68o18nIiv8Yg172b0BWWvtbrizYW9424bBz1tvag0C msiVO2qyE7/yaU5Ph0nyVME+1j5aek9BMN+O1YkZlzNv7ruFIL2TQ1ZXKg9LH49W9wSx kqIg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j13-20020a056a00174d00b005583264623csi38241015pfc.278.2022.10.24.04.11.15; Mon, 24 Oct 2022 04:11:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229782AbiJXKkV convert rfc822-to-8bit (ORCPT + 99 others); Mon, 24 Oct 2022 06:40:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229730AbiJXKkQ (ORCPT ); Mon, 24 Oct 2022 06:40:16 -0400 Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CFE033B463; Mon, 24 Oct 2022 03:40:11 -0700 (PDT) Received: from omf03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 51226AB064; Mon, 24 Oct 2022 10:40:09 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: joe@perches.com) by omf03.hostedemail.com (Postfix) with ESMTPA id E2CF96000A; Mon, 24 Oct 2022 10:40:03 +0000 (UTC) Message-ID: <6b9b7f9d835a271312bd5955d96b83bd14c9e6fa.camel@perches.com> Subject: Re: [PATCH v4 3/3] MAINTAINERS: Add KX022A maintainer entry From: Joe Perches To: "Vaittinen, Matti" , Matti Vaittinen Cc: Jonathan Cameron , Lars-Peter Clausen , Rob Herring , Krzysztof Kozlowski , Andy Shevchenko , Dmitry Rokosov , Nikita Yushchenko , Cosmin Tanislav , Jagath Jog J , "linux-iio@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Date: Mon, 24 Oct 2022 03:40:01 -0700 In-Reply-To: <0c1471c0-b6b0-7b2b-62af-d3221edeeac4@fi.rohmeurope.com> References: <92c3f72e60bc99bf4a21da259b4d78c1bdca447d.camel@perches.com> <0c1471c0-b6b0-7b2b-62af-d3221edeeac4@fi.rohmeurope.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8BIT User-Agent: Evolution 3.44.4 (3.44.4-2.fc36) MIME-Version: 1.0 X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_SPF_HELO, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS, SPF_NONE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.6 X-Stat-Signature: r4mtm9zbjpfjaacgghcjpwpq8aruqopy X-Rspamd-Server: rspamout08 X-Rspamd-Queue-Id: E2CF96000A X-Session-Marker: 6A6F6540706572636865732E636F6D X-Session-ID: U2FsdGVkX1+NCoWF+QkD4EYH2wNG31bmSVo7//aomnU= X-HE-Tag: 1666608003-170265 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > > --- > > > 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 > > > +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" there should be an individual listed as its actual maintainer, not just a person that might review submitted patches. 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.