From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
linux-edac@vger.kernel.org, linux-hams@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] MAINTAINERS: Deal with the linux-mips.org mess
Date: Tue, 12 Nov 2024 16:10:40 +0100 [thread overview]
Message-ID: <ZzNv8PWzPsxiuPSN@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2411121327130.9262@angie.orcam.me.uk>
On Tue, Nov 12, 2024 at 01:47:17PM +0000, Maciej W. Rozycki wrote:
> Hi,
>
> Here's v2 of the patch series to address Ralf Baechle to have stopped
> responding and linux-mips.org gone down, and Thomas stepping up as a
> replacement maintainer. This has been regenerated against the current
> version of MAINTAINERS. Please apply.
>
> Previous iterations:
>
> - v1 at: <https://lore.kernel.org/r/alpine.DEB.2.21.2410131952550.40463@angie.orcam.me.uk/>.
I didn't see this mail, but the v2 series in patchwork...
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:[~2024-11-12 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:47 Maciej W. Rozycki
2024-11-12 13:47 ` [PATCH v2 1/2] MAINTAINERS: Retire Ralf Baechle Maciej W. Rozycki
2024-11-13 10:05 ` Geert Uytterhoeven
2024-11-12 13:47 ` [PATCH v2 2/2] MAINTAINERS: Remove linux-mips.org references Maciej W. Rozycki
2024-11-12 14:27 ` [PATCH v2 0/2] MAINTAINERS: Deal with the linux-mips.org mess Konstantin Ryabitsev
2024-11-12 15:10 ` 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=ZzNv8PWzPsxiuPSN@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=konstantin@linuxfoundation.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
/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®