From: Conor Dooley <conor@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: palmer@dabbelt.com, arnd@arndb.de, linux-next@vger.kernel.org
Subject: Re: RISC-V DT/SoC branch changes
Date: Wed, 16 Nov 2022 22:37:34 +0000 [thread overview]
Message-ID: <Y3VmLtVSkpf4vHYb@spud> (raw)
In-Reply-To: <20221117093010.74cf9d0a@canb.auug.org.au>
On Thu, Nov 17, 2022 at 09:30:10AM +1100, Stephen Rothwell wrote:
> 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.
Great, thanks a mill Stephen.
prev parent reply other threads:[~2022-11-16 22:37 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
2022-11-16 22:37 ` Conor Dooley [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=Y3VmLtVSkpf4vHYb@spud \
--to=conor@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=sfr@canb.auug.org.au \
/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).