From: "Arnd Bergmann" <arnd@arndb.de>
To: "Conor.Dooley" <conor.dooley@microchip.com>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Should we merge arch/riscv/boot/dts via the SOC tree?
Date: Wed, 09 Nov 2022 08:49:11 +0100 [thread overview]
Message-ID: <ea8d23d3-541a-4366-b77f-861d0a9cc5ca@app.fastmail.com> (raw)
In-Reply-To: <Y2puchRvbo6+YJSy@wendy>
On Tue, Nov 8, 2022, at 15:57, Conor Dooley wrote:
> On Tue, Nov 08, 2022 at 02:42:16PM +0100, Arnd Bergmann wrote:
>
> I assume your ommission of the SiFive bit from this mail means you're
> happy enough with it?
Yes, that's fine.
Arnd
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-11-09 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 16:46 Should we merge arch/riscv/boot/dts via the SOC tree? Palmer Dabbelt
2022-11-07 17:51 ` Krzysztof Kozlowski
2022-11-13 15:52 ` Icenowy Zheng
2022-11-07 18:31 ` Conor Dooley
2022-11-08 12:51 ` Arnd Bergmann
2022-11-08 13:32 ` Conor Dooley
2022-11-08 13:42 ` Arnd Bergmann
2022-11-08 14:57 ` Conor Dooley
2022-11-09 7:49 ` Arnd Bergmann [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=ea8d23d3-541a-4366-b77f-861d0a9cc5ca@app.fastmail.com \
--to=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=linux-riscv@lists.infradead.org \
--cc=nicolas.ferre@microchip.com \
/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).