From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Michael Hennerich <Michael.Hennerich@analog.com>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, Pavel Machek <pavel@ucw.cz>,
Tim Harvey <tharvey@gateworks.com>,
Robert Jones <rjones@gateworks.com>, Lee Jones <lee@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Sebastian Reichel <sre@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Ricardo Rivera-Matos <r-rivera-matos@ti.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-fbdev@vger.kernel.org, linux-leds@vger.kernel.org,
netdev@vger.kernel.org, linux-pm@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/5] iio/hwmon/mfd/leds/net/power/ASoC: dt-bindings: few stale maintainers cleanup
Date: Tue, 9 Aug 2022 08:25:29 +0300 [thread overview]
Message-ID: <c6b890b6-e72f-0377-f0ae-cd15d29c23a1@linaro.org> (raw)
In-Reply-To: <20220808115202.3175eb1f@kernel.org>
On 08/08/2022 21:52, Jakub Kicinski wrote:
> On Mon, 8 Aug 2022 13:47:07 +0300 Krzysztof Kozlowski wrote:
>> Several of the bindings here had only one
>> maintainer and history does not always point to a new one (although I did not
>> perform extensive digging). I added subsystem maintainer, because dtschema
>> requires such entry. This is not the best choice as simply subsystem maintainer
>> might not have the actual device (or its datasheets or any interest in it).
>>
>> However dtschema requires a maintainer. Maybe we could add some
>> "orphaned" entry in such case?
>
> Integrating it with MAINTAINERS would be another option worth exploring
> although slightly tangential.
>
> How do you want this merged? It's all over the place subsystem-wise.
I was thinking this could go via Rob's tree as fixes for current cycle,
so your Ack would be great. If there is preference, I can split it per
subsystem, but for such trivial updates it's a bit of a churn.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-09 5:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 10:47 [PATCH 0/5] iio/hwmon/mfd/leds/net/power/ASoC: dt-bindings: few stale maintainers cleanup Krzysztof Kozlowski
2022-08-08 10:47 ` [PATCH 1/5] dt-bindings: iio: Drop Joachim Eastwood Krzysztof Kozlowski
2022-08-08 13:59 ` Jonathan Cameron
2022-08-08 10:47 ` [PATCH 2/5] dt-bindings: iio: Drop Bogdan Pricop Krzysztof Kozlowski
2022-08-08 13:58 ` Jonathan Cameron
2022-08-08 10:47 ` [PATCH 3/5] dt-bindings: Drop Beniamin Bia and Stefan Popa Krzysztof Kozlowski
2022-08-08 13:57 ` Jonathan Cameron
2022-08-08 10:47 ` [PATCH 4/5] dt-bindings: Drop Robert Jones Krzysztof Kozlowski
2022-08-08 13:56 ` Jonathan Cameron
2022-08-08 10:47 ` [PATCH 5/5] dt-bindings: Drop Dan Murphy Krzysztof Kozlowski
2022-08-08 11:08 ` Krzysztof Kozlowski
2022-08-08 15:04 ` Andrew Davis
2022-08-08 20:08 ` Andrew Lunn
2022-08-08 20:32 ` Andrew Davis
2022-08-08 20:41 ` Andrew Lunn
2022-08-09 4:34 ` Krzysztof Kozlowski
2022-08-08 13:56 ` Jonathan Cameron
2022-08-09 18:24 ` Jakub Kicinski
2022-08-08 18:52 ` [PATCH 0/5] iio/hwmon/mfd/leds/net/power/ASoC: dt-bindings: few stale maintainers cleanup Jakub Kicinski
2022-08-09 5:25 ` Krzysztof Kozlowski [this message]
2022-08-09 18:23 ` Jakub Kicinski
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=c6b890b6-e72f-0377-f0ae-cd15d29c23a1@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Michael.Hennerich@analog.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@ucw.cz \
--cc=r-rivera-matos@ti.com \
--cc=rjones@gateworks.com \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--cc=tharvey@gateworks.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).