From: Paul Walmsley <paul.walmsley@sifive.com>
To: linux-riscv@lists.infradead.org
Cc: palmerdabbelt@google.com, linux-kernel@vger.kernel.org
Subject: RISC-V v5.6 patches will be collected by Palmer
Date: Mon, 9 Dec 2019 09:43:04 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912090933500.308630@viisi.sifive.com> (raw)
Folks,
Most of the backlog of the RISC-V kernel patches from the past few months
have been cleared, and now Palmer has graciously volunteered to handle the
patch collection for v5.6 and to send those upstream to Linus.
I'll continue to handle the v5.5-rc patches and pull requests, and will
try to take care of some of the patches that have already been posted.
Anything that doesn't make it will be handed off to Palmer.
So pretty much any non-fix patches posted from now on will go to v5.6.
If anyone has any questions, feel free to discuss them here.
- Paul
reply other threads:[~2019-12-09 17:43 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=alpine.DEB.2.21.9999.1912090933500.308630@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmerdabbelt@google.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).