From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Conor Dooley <conor@kernel•org>
Cc: palmer@dabbelt•com, arnd@arndb•de, linux-next@vger•kernel.org
Subject: Re: RISC-V DT/SoC branch changes
Date: Thu, 17 Nov 2022 09:30:10 +1100 [thread overview]
Message-ID: <20221117093010.74cf9d0a@canb.auug.org.au> (raw)
In-Reply-To: <Y3PqngfnCG/jVyJp@spud>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Hi Conor,
On Tue, 15 Nov 2022 19:38:06 +0000 Conor Dooley <conor@kernel•org> wrote:
>
> Currently you've got two of my branches in linux-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ dt-for-next
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ dt-fixes
> which are named risc-v-mc and risc-v-mc-fixes respectively iirc.
>
> We're doing some re-jigging in RISC-V land, and I'm gonna be taking
> patches for other RISC-V devicetrees in addition to the Microchip ones.
> I'll also taking patches for drivers/soc that are for RISC-V SoCs.
> The PRs for both will be made against the soc tree rather than the RISC-V
> one.
>
> Would it be possible to drop my existing two trees & add:
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-dt-for-next
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-dt-fixes
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-soc-for-next
> https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-soc-fixes
All done from today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-11-16 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 19:38 RISC-V DT/SoC branch changes Conor Dooley
2022-11-16 22:30 ` Stephen Rothwell [this message]
2022-11-16 22:37 ` Conor Dooley
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=20221117093010.74cf9d0a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=conor@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=palmer@dabbelt$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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