linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Nuno Sa <nuno.sa@analog.com>,
	David Lechner <dlechner@baylibre.com>,
	Dumitru Ceclan <mitrutzceclan@gmail.com>,
	Trevor Gamblin <tgamblin@baylibre.com>,
	Matteo Martelli <matteomartelli3@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [RFC PATCH 4/5] pinctrl: Support ROHM BD79124 pinmux / GPO
Date: Thu, 13 Feb 2025 14:10:47 +0200	[thread overview]
Message-ID: <74331ea3-d292-4048-8bdb-32d089b151a6@gmail.com> (raw)
In-Reply-To: <CACRpkdYMytiXoXrjTX3ts6ce1T6Xf4rSyk=sDP9fYz730Q-3bQ@mail.gmail.com>

On 13/02/2025 13:53, Linus Walleij wrote:
> On Thu, Feb 6, 2025 at 11:09 AM Matti Vaittinen
> <mazziesaccount@gmail.com> wrote:
> 
>> I just realized I should've shared the link to the v2 - which may not
>> include all the recipients (because it no longer touches all the
>> subsystems - and the get_maintainer.pl probably reduced the list of
>> recipients). So, for anyone interested, here's the v2:
>>
>> https://lore.kernel.org/all/cover.1738761899.git.mazziesaccount@gmail.com/
> 
> Well it touches (uses) the gpio subsystem so the GPIO maintainers
> should have been on CC...
 > > This is one of the shortcomings of get_maintainers.pl really (also what
> b4 is using): it does not know that if you use some specific APIs from
> some specific .h files then some specific maintainers need to be on
> CC.
> 
> It's because there is no hard rule: <linux/slab.h> - who cares? It's not
> like the memory management people want to look at every user of
> kmalloc()... <linux/gpio/driver.h> - this is a different story because
> it's possible to get the semantics wrong.

This is a tough one. There are also a few other subsystems (besides mm) 
where maintainers can't stay on track for all the users. Also, AFAIR, 
some maintainers don't want to be CC'd by users of their subsystems, but 
only care the subsystem core changes. It's hard for an occasional 
contributor to know who to CC - it's often safest to just go with the 
get_maintainer.pl.

Still, I recognize the problem. I'm also trying to review users of some 
of the APIs I've added to IIO, lib or regulator subsystems. What I use 
is for this is lore + lei which fetch me mails with specific keywords 
(APIs / API prefixes / headers which I'm interested in) from the mail 
lists. Regular email filters could also do the job, but it'd required 
subscribing the lists which tend to quickly fill ones mailboxes.

Anyways, I believe it'd be best if maintainers who want to review users 
of their APIs did pick the mails with specific keywords from the lists. 
Maintainers know what they want to pick, (occasional) patch senders can 
only guess this ;)

> That said, I looked at the patch in lore:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> for patch 4/5!

Thanks! I do appreciate all the reviews as usual!

Yours,
   -- Matti


  reply	other threads:[~2025-02-13 12:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 13:34 [RFC PATCH 0/5] Support ROHM BD79124 ADC/GPO Matti Vaittinen
2025-01-31 13:36 ` [RFC PATCH 1/5] dt-bindings: " Matti Vaittinen
2025-01-31 13:37 ` [RFC PATCH 2/5] mfd: Add " Matti Vaittinen
2025-01-31 17:14   ` Jonathan Cameron
2025-02-01 16:04     ` Matti Vaittinen
2025-02-05 13:40   ` Matti Vaittinen
2025-01-31 13:37 ` [RFC PATCH 3/5] iio: adc: Support ROHM BD79124 ADC Matti Vaittinen
2025-01-31 17:41   ` Jonathan Cameron
2025-02-01 15:38     ` Matti Vaittinen
2025-02-01 16:26       ` Jonathan Cameron
2025-02-05 13:58     ` Matti Vaittinen
2025-02-08 13:01       ` Jonathan Cameron
2025-01-31 13:38 ` [RFC PATCH 4/5] pinctrl: Support ROHM BD79124 pinmux / GPO Matti Vaittinen
2025-02-05 13:40   ` Matti Vaittinen
2025-02-06  9:39     ` Linus Walleij
2025-02-06 10:05       ` Matti Vaittinen
2025-02-06 10:09       ` Matti Vaittinen
2025-02-13 11:53         ` Linus Walleij
2025-02-13 12:10           ` Matti Vaittinen [this message]
2025-02-13 16:18           ` David Lechner
2025-01-31 13:38 ` [RFC PATCH 5/5] MAINTAINERS: Add ROHM BD79124 ADC/GPO Matti Vaittinen
2025-01-31 17:08 ` [RFC PATCH 0/5] Support " Jonathan Cameron
2025-02-01 15:00   ` Matti Vaittinen
2025-02-01 16:30     ` Jonathan Cameron
2025-02-01 17:12       ` Matti Vaittinen

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=74331ea3-d292-4048-8bdb-32d089b151a6@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lee@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteomartelli3@gmail.com \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=mitrutzceclan@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=tgamblin@baylibre.com \
    /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).