From: Paul Walmsley <pjw@kernel.org>
To: linux-riscv@lists.infradead.org
Cc: palmer@dabbelt.com, alex@ghiti.fr
Subject: Helping out with arch/riscv maintenance
Date: Fri, 5 Sep 2025 16:32:01 -0600 (MDT) [thread overview]
Message-ID: <4620eefc-8304-85a5-5a89-dcc6610edbfb@kernel.org> (raw)
Hi folks,
At Palmer's request, I'll be helping out with arch/riscv maintenance for a
little while. Palmer's been doing a great job, and I'm sure I won't be
able to do as good of a job as he's been doing. Let's see if we can keep
things moving smartly in the interim.
As you may have seen, a fixes PR was just sent to Linus. Many of the
patches were initially collected by Alex Ghiti, and I borrowed some of his
curation work for that branch - thanks very much, Alex. Will plan to send
at least one more set of fixes to Linus before the merge window.
Some of my local kernel maintenance infrastructure is a bit out of date.
I'll be cleaning that up over the next few weeks. Thanks for your
patience while that gets updated.
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2025-09-06 0:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4620eefc-8304-85a5-5a89-dcc6610edbfb@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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