[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb8891d4-de4e-493c-9914-0391b3baf212@kernel.org>
Date: Fri, 4 Jul 2025 11:15:43 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ben Zong-You Xie <ben717@...estech.com>
Cc: arnd@...db.de, paul.walmsley@...ive.com, palmer@...belt.com,
aou@...s.berkeley.edu, alex@...ti.fr, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, tglx@...utronix.de, daniel.lezcano@...aro.org,
prabhakar.mahadev-lad.rj@...renesas.com, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
soc@...ts.linux.dev, tim609@...estech.com
Subject: Re: [PATCH 0/8] add Voyager board support
On 04/07/2025 10:14, Ben Zong-You Xie wrote:
> The Voyager is a 9.6” x 9.6” Micro ATX form factor development board
> including Andes QiLai SoC. This patch series adds minimal device tree
> files for the QiLai SoC and the Voyager board [1].
>
> Now only support basic uart drivers to boot up into a basic console. Other
> features will be added later.
>
> The original patchset [2] has been reviewed positively in relevant mailing
> lists. Thus, send a new patchset to soc@...ts.linux.dev .
>
> Also, there is a patch dependency in this patchset:
> Patch 2 <- Patch 4 <- Patch 5 <- Patch 6
How? These are bindings. How DTS can depend on the binding? Do you have
akcs from their subsystem maintainers that you are sending it here?
Sorry, but no, this should go via their maintainers, unless they did not
want to pick it up. Is this the case here?
Best regards,
Krzysztof
Powered by blists - more mailing lists