[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <090d0e196fd0f814b5385f2c6e47e5196f0be649.camel@codeconstruct.com.au>
Date: Thu, 25 Sep 2025 09:46:51 +0930
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Kevin Tung <kevin.tung.openbmc@...il.com>
Cc: Rob Herring <robh@...nel.org>, Andrew Lunn <andrew@...n.ch>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Joel
Stanley <joel@....id.au>, Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH v1 0/2] Add Meta (Facebook) Yosemite5 BMC (AST2600)
Hi Kevin,
On Wed, 2025-09-24 at 08:34 -0500, Rob Herring wrote:
> On Wed, Sep 24, 2025 at 8:05 AM Kevin Tung <kevin.tung.openbmc@...il.com> wrote:
> > I also checked the work with `make CHECK_DTBS=y
> > aspeed/aspeed-bmc-facebook- yosemite5.dtb`,
> > and the warnings that appear are not related to these patches.
>
> Um, they are related because they are warnings for *your* platform.
> You don't care that there are warnings for your platform?
Which is to say, by contributing a DTS that relies on the ASPEED DTSIs
you're now part of the community of people interested in maintaining
support for ASPEED SoCs in the kernel, and it will be appreciated if
you could help improve what we have.
If you could pick a warning or two from the DTSIs and contribute
changes to address them that'd be great, as this improves the situation
for everyone.
Andrew
Powered by blists - more mailing lists