All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: conor@kernel.org, palmer@dabbelt.com, arnd@arndb.de,
	linux-next@vger.kernel.org
Subject: RISC-V DT/SoC branch changes
Date: Tue, 15 Nov 2022 19:38:06 +0000	[thread overview]
Message-ID: <Y3PqngfnCG/jVyJp@spud> (raw)

Hey Stephen,

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

Please LMK if you need any more information.

Thanks,
Conor.


             reply	other threads:[~2022-11-15 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 19:38 Conor Dooley [this message]
2022-11-16 22:30 ` RISC-V DT/SoC branch changes Stephen Rothwell
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=Y3PqngfnCG/jVyJp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.