From: Joe Perches <joe@perches.com>
To: Paul Burton <paulburton@kernel.org>, linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes
Date: Wed, 19 Feb 2020 19:08:30 -0800 [thread overview]
Message-ID: <cfeab22c0f332418d25e56fa86f5420f5470e4ee.camel@perches.com> (raw)
In-Reply-To: <20200219191730.1277800-3-paulburton@kernel.org>
On Wed, 2020-02-19 at 11:17 -0800, Paul Burton wrote:
> My time with MIPS the company has reached its end, and so at best I'll
> have little time spend on maintaining arch/mips/. Reflect that in
> MAINTAINERS by changing status to Odd Fixes. Hopefully this might spur
> the involvement of someone with more time, but even if not it should
> help serve to avoid unrealistic expectations.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -11120,7 +11120,7 @@ W: http://www.linux-mips.org/
> T: git git://git.linux-mips.org/pub/scm/ralf/linux.git
Maybe Ralf's T: entry should be removed too.
next prev parent reply other threads:[~2020-02-20 3:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:17 [PATCH 0/2] MAINTAINERS: Update MIPS entry Paul Burton
2020-02-19 19:17 ` [PATCH 1/2] MAINTAINERS: Remove Ralf Baechle as MIPS maintainer Paul Burton
2020-02-19 19:17 ` [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes Paul Burton
2020-02-20 3:08 ` Joe Perches [this message]
2020-02-20 6:44 ` Huacai Chen
2020-02-20 7:55 ` Jiaxun Yang
2020-02-20 11:23 ` Thomas Bogendoerfer
2020-02-20 12:11 ` YunQiang Su
2020-02-20 12:40 ` Zhou Yanjie
2020-02-20 17:01 ` YunQiang Su
2020-02-20 17:36 ` Zhou Yanjie
2020-02-22 10:41 ` Thomas Bogendoerfer
2020-02-22 16:08 ` Paul Cercueil
2020-02-22 17:54 ` Jiaxun Yang
2020-02-24 8:37 ` Philippe Mathieu-Daudé
2020-02-24 13:50 ` Paul Cercueil
2020-02-24 10:53 ` Thomas Bogendoerfer
2020-02-20 8:14 Jiaxun Yang
2020-02-20 10:06 ` Zhou Yanjie
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=cfeab22c0f332418d25e56fa86f5420f5470e4ee.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@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;
as well as URLs for NNTP newsgroup(s).