From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Rahul Bedarkar <rahulbedarkar89@gmail.com>,
linux-mips@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: adjust PISTACHIO SOC SUPPORT after its retirement
Date: Sat, 21 Aug 2021 10:41:24 +0200 [thread overview]
Message-ID: <20210821084124.GB3555@alpha.franken.de> (raw)
In-Reply-To: <20210816105326.8050-1-lukas.bulwahn@gmail.com>
On Mon, Aug 16, 2021 at 12:53:26PM +0200, Lukas Bulwahn wrote:
> Commit 104f942b2832 ("MIPS: Retire MACH_PISTACHIO") removes
> ./arch/mips/pistachio/ and ./arch/mips/configs/pistachio_defconfig, but
> misses to adjust the corresponding section PISTACHIO SOC SUPPORT
> in MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file matches F: arch/mips/configs/pistachio*_defconfig
> warning: no file matches F: arch/mips/pistachio/
>
> As James Hartley is not reachable with the provided email address, the
> remaining dtsi file, arch/mips/boot/dts/img/pistachio.dtsi, must be
> maintained by its only user pistachio_marduk.dts, which is part of MARDUK
> (CREATOR CI40) DEVICE TREE SUPPORT.
>
> Add maintenance of pistachio.dtsi to that section and drop the PISTACHIO
> SOC SUPPORT after its retirement.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on next-20210816
>
> Jiaxun, Rahul, please ack.
> Thomas, please pick this minor non-urgent clean-up patch on mips-next.
>
> MAINTAINERS | 10 +---------
> 1 file changed, 1 insertion(+), 9 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-08-21 9:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 10:53 [PATCH v2] MAINTAINERS: adjust PISTACHIO SOC SUPPORT after its retirement Lukas Bulwahn
2021-08-17 5:21 ` Rahul Bedarkar
2021-08-17 7:28 ` Jiaxun Yang
2021-08-21 8:41 ` Thomas Bogendoerfer [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=20210821084124.GB3555@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rahulbedarkar89@gmail.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).