From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, arm <arm@kernel.org>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>
Cc: "Lennert Buytenhek" <kernel@wantstofly.org>,
"Steve Sakoman" <sakoman@gmail.com>,
"Mark F . Brown" <mark.brown314@gmail.com>,
"Robert Jarzmik" <robert.jarzmik@free.fr>,
"Florian Fainelli" <florian@openwrt.org>,
"Simtec Linux Team" <linux@simtec.co.uk>
Subject: Re: [PATCH] ARM: MAINTAINERS: drop empty entries for removed boards
Date: Tue, 02 Jan 2024 10:25:32 +0100 [thread overview]
Message-ID: <eb2fa9be-8ef1-4ebf-a8c0-ede082bbe1a4@app.fastmail.com> (raw)
In-Reply-To: <aaeb97f1-075e-44b9-874d-f66763ef8866@linaro.org>
On Mon, Dec 18, 2023, at 15:39, Krzysztof Kozlowski wrote:
> On 18/12/2023 15:21, Arnd Bergmann wrote:
>> On Mon, Dec 18, 2023, at 13:45, Krzysztof Kozlowski wrote:
>>
>> drivers/mmc/host/pxamci.c and drivers/rtc/rtc-pxa.c
>> are still in use.
>
> MMCI does not have maintainer.
>
> For the RTC, I guess the intention of 57f63bc8fe79 ("rtc: update
> maintainership of pxa rtc driver") was to maintain the driver.
>
> The actual problem is that all of these entries (and R-321X below) come
> from the times people were not putting any file paths to MAINTAINERS.
> They stayed like this for 15-17 years, thus being effectively noop.
>
> Let's maybe wait till any of Cc-ed people respond and confirm they want
> to grow the maintainer entry to cover the files? If they don't come, I
> propose to remove them.
Nobody else replied now, so for the moment, I applied a partial
patch removing the EDB9315A, TS7250, TETON and CATS entries that
are for files that were removed or are in the process.
For the other ones, I would still prefer to just list the files.
Arnd
prev parent reply other threads:[~2024-01-02 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 13:45 Krzysztof Kozlowski
2023-12-18 14:21 ` Arnd Bergmann
2023-12-18 14:39 ` Krzysztof Kozlowski
2024-01-02 9:25 ` Arnd Bergmann [this message]
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=eb2fa9be-8ef1-4ebf-a8c0-ede082bbe1a4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=florian@openwrt.org \
--cc=kernel@wantstofly.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@simtec.co.uk \
--cc=mark.brown314@gmail.com \
--cc=olof@lixom.net \
--cc=robert.jarzmik@free.fr \
--cc=sakoman@gmail.com \
--cc=soc@kernel.org \
/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
all inboxes | Powered by JetHome®