From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89D53FA3740 for ; Mon, 24 Oct 2022 11:08:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229967AbiJXLI6 convert rfc822-to-8bit (ORCPT ); Mon, 24 Oct 2022 07:08:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229929AbiJXLIy (ORCPT ); Mon, 24 Oct 2022 07:08:54 -0400 Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E3F6DD5; Mon, 24 Oct 2022 04:08:53 -0700 (PDT) Received: from omf11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 79AD1AB063; Mon, 24 Oct 2022 11:08:51 +0000 (UTC) Received: from [HIDDEN] (Authenticated sender: joe@perches.com) by omf11.hostedemail.com (Postfix) with ESMTPA id 733B02002A; Mon, 24 Oct 2022 11:08:32 +0000 (UTC) Message-ID: 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 04:08:42 -0700 In-Reply-To: <57582495-210b-f9c2-db80-e2ddbc76e7c3@fi.rohmeurope.com> References: <92c3f72e60bc99bf4a21da259b4d78c1bdca447d.camel@perches.com> <0c1471c0-b6b0-7b2b-62af-d3221edeeac4@fi.rohmeurope.com> <6b9b7f9d835a271312bd5955d96b83bd14c9e6fa.camel@perches.com> <57582495-210b-f9c2-db80-e2ddbc76e7c3@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-Rspamd-Queue-Id: 733B02002A X-Stat-Signature: u34dxm34bxifdbdufa5u3fzdrk6yibc7 X-Rspamd-Server: rspamout04 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Session-ID: U2FsdGVkX18wOOIOmP0JikBbFObxF4cZ4V5fSQ+Yo5k= X-HE-Tag: 1666609712-932372 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org 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.