From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>, geert+renesas@glider.be
Cc: prabhakar.csengg@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, geert+renesas@glider.be,
magnus.damm@gmail.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, heiko@sntech.de,
Conor Dooley <conor.dooley@microchip.com>,
guoren@kernel.org, anup@brainfault.org,
Atish Patra <atishp@rivosinc.com>,
heinrich.schuchardt@canonical.com, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
prabhakar.mahadev-lad.rj@bp.renesas.com
Subject: Re: [PATCH v5 0/7] Add support for Renesas RZ/Five SoC
Date: Wed, 9 Nov 2022 21:21:01 +0000 [thread overview]
Message-ID: <Y2wZvZLAENWh6qvs@spud> (raw)
In-Reply-To: <mhng-563fb6cf-4505-4137-8da1-13f631e1c74f@palmer-ri-x1c9a>
On Wed, Nov 09, 2022 at 11:55:24AM -0800, Palmer Dabbelt wrote:
> On Fri, 28 Oct 2022 09:59:14 PDT (-0700), prabhakar.csengg@gmail.com wrote:
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > Lad Prabhakar (7):
> > dt-bindings: riscv: Sort the CPU core list alphabetically
> > dt-bindings: riscv: Add Andes AX45MP core to the list
> > riscv: Kconfig.socs: Add ARCH_RENESAS kconfig option
> > riscv: dts: renesas: Add initial devicetree for Renesas RZ/Five SoC
> > riscv: dts: renesas: Add minimal DTS for Renesas RZ/Five SMARC EVK
> > MAINTAINERS: Add entry for Renesas RISC-V
> > riscv: configs: defconfig: Enable Renesas RZ/Five SoC
> Geert was mentioning taking these though one of his trees, that works for me
> so
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> Happy to do a shared tag or whatever, but I think we can just skip that
> here. The only conflicts would be defconfig and Kconfig.socs, but I don't
> think anything big is in the works for either -- unless Conor was planning
> on re-spinning that Kconfig.socs rework?
Uh, nah. I've got a wee bit (the removal of selects) that is "ready" but
there's zero urgency so it can wait for after v6.2-rc1. I don't think
it'd conflict anyway. The rest of it I need to sort out a v1 of, but I've
been distracted. Should be safe to take the defconfig & Kconfig.socs stuff
in terms of me doing anything.
Geert, would you be able to apply the first two patches on top of
v6.1-rc1 just in case, as you mentioned previously, it needs to become
part of a shared branch? Seems unlikely at this point in the cycle
though.
Thanks,
Conor.
next prev parent reply other threads:[~2022-11-09 21:21 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 16:59 [PATCH v5 0/7] Add support for Renesas RZ/Five SoC Prabhakar
2022-10-28 16:59 ` [PATCH v5 1/7] dt-bindings: riscv: Sort the CPU core list alphabetically Prabhakar
2022-10-29 4:20 ` Guo Ren
2022-10-28 16:59 ` [PATCH v5 2/7] dt-bindings: riscv: Add Andes AX45MP core to the list Prabhakar
2022-10-29 4:20 ` Guo Ren
2022-10-28 16:59 ` [PATCH v5 3/7] riscv: Kconfig.socs: Add ARCH_RENESAS kconfig option Prabhakar
2022-10-29 4:18 ` Guo Ren
2022-11-08 15:37 ` Geert Uytterhoeven
2022-10-28 16:59 ` [PATCH v5 4/7] riscv: dts: renesas: Add initial devicetree for Renesas RZ/Five SoC Prabhakar
2022-10-29 4:25 ` Guo Ren
2022-10-29 19:10 ` Lad, Prabhakar
2022-10-30 0:02 ` Guo Ren
2022-10-30 18:16 ` Conor Dooley
2022-10-30 22:27 ` Lad, Prabhakar
2022-10-30 22:39 ` Conor Dooley
2022-10-31 1:11 ` Guo Ren
2022-10-31 0:45 ` Guo Ren
2022-10-30 22:23 ` Lad, Prabhakar
2022-11-08 15:43 ` Geert Uytterhoeven
2022-10-28 16:59 ` [PATCH v5 5/7] riscv: dts: renesas: Add minimal DTS for Renesas RZ/Five SMARC EVK Prabhakar
2022-10-29 4:26 ` Guo Ren
2022-10-29 19:14 ` Lad, Prabhakar
2022-11-08 15:44 ` Geert Uytterhoeven
2022-10-28 16:59 ` [PATCH v5 6/7] MAINTAINERS: Add entry for Renesas RISC-V Prabhakar
2022-10-29 4:27 ` Guo Ren
2022-10-28 16:59 ` [PATCH v5 7/7] riscv: configs: defconfig: Enable Renesas RZ/Five SoC Prabhakar
2022-10-29 4:28 ` Guo Ren
2022-11-08 15:51 ` Geert Uytterhoeven
2022-11-08 16:06 ` Lad, Prabhakar
2022-11-08 16:12 ` Geert Uytterhoeven
2022-11-08 17:22 ` Lad, Prabhakar
2022-11-08 19:19 ` Geert Uytterhoeven
2022-11-08 22:01 ` Lad, Prabhakar
2022-11-09 7:46 ` Geert Uytterhoeven
2022-11-09 9:16 ` Lad, Prabhakar
2022-10-30 18:24 ` [PATCH v5 0/7] Add support for " Conor Dooley
2022-10-30 22:37 ` Lad, Prabhakar
2022-10-30 22:45 ` Conor Dooley
2022-10-30 23:01 ` Lad, Prabhakar
2022-11-07 18:03 ` Lad, Prabhakar
2022-11-07 18:17 ` Conor Dooley
2022-11-08 16:02 ` Geert Uytterhoeven
2022-11-08 19:29 ` Conor Dooley
2022-11-09 19:55 ` Palmer Dabbelt
2022-11-09 21:21 ` Conor Dooley [this message]
2022-11-10 16:17 ` Geert Uytterhoeven
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=Y2wZvZLAENWh6qvs@spud \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=magnus.damm@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).