From: Drew Fustini <fustini@kernel.org>
To: broonie@kernel.org
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-riscv@lists.infradead.org
Subject: Add fustini riscv-config to linux-next
Date: Tue, 9 Jun 2026 00:21:48 -0700 [thread overview]
Message-ID: <aie/DAyvda4bcdLm@x1> (raw)
Hi Mark,
I have a new tree where I will apply patches for riscv defconfigs. I
have trees for dt and clk for two riscv soc vendors in next but
defconfig patches don't belong in such branches. Conor has in the past
taken defconfig patches but he is happy for me to send pull requests
as needed based on my new defconfig branches.
Please add these to linux-next:
riscv-config https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-for-next
riscv-config-fixes https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git#riscv-config-fixes
Thanks,
Drew
next reply other threads:[~2026-06-09 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 7:21 Drew Fustini [this message]
2026-06-09 11:18 ` Add fustini riscv-config to linux-next Mark Brown
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=aie/DAyvda4bcdLm@x1 \
--to=fustini@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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