From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Paul Burton <paulburton@kernel.org>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes
Date: Mon, 24 Feb 2020 11:53:45 +0100 [thread overview]
Message-ID: <20200224105345.GA8335@alpha.franken.de> (raw)
In-Reply-To: <1582387719.3.1@crapouillou.net>
On Sat, Feb 22, 2020 at 01:08:39PM -0300, Paul Cercueil wrote:
> So I think Thomas is the best candidate to be maintainer, since he has both
> experience and free time ;)
>
> I'm sort-of the maintainer for the Ingenic platform and drivers, if Jiaxun
> wants to do the same for Loongson hardware, that would make Thomas' job
> easier. Having three co-maintainers with equal rights would be a total mess.
perfect for me, thank you for your support.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-02-24 10:57 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20200224105345.GA8335@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.