From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rob Herring <robh@kernel.org>, Donald Shannon <donalds@nvidia.com>
Cc: conor+dt@kernel.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, krzk+dt@kernel.org,
joel@jms.id.au, linux-aspeed@lists.ozlabs.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b
Date: Thu, 31 Jul 2025 11:41:19 +0930 [thread overview]
Message-ID: <2de9da0e95d3e1284a29170c99f7b69baadb9518.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAL_JsqJwgbWa0sPVgdxMchPfa1hR8o-=wRh4UgoK3QfDdW+S+g@mail.gmail.com>
On Thu, 2025-07-24 at 22:25 -0500, Rob Herring wrote:
>
> All of the below warnings you are introducing...
>
> And yeah, all the ones above are existing, but I don't see a lot of
> progress fixing them. It seems no one adding their board cares about
> the SoC warnings given the lack of progress on aspeed stuff. Maybe new
> boards need to be rejected without some improvements...
>
I had an old branch with a series that reduces the warnings. I'll
rebase it and tidy it up a bit wrt more recent binding submissions.
Once it's mostly sensible I'll consider pointing people to it as
suggestions for fixing existing issues on the path to getting their own
devicetrees merged.
Andrew
prev parent reply other threads:[~2025-07-31 2:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 22:23 [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b Donald Shannon
2025-07-23 22:23 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board Donald Shannon
2025-07-24 7:54 ` Krzysztof Kozlowski
2025-07-23 22:23 ` [PATCH v7 2/2] ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board Donald Shannon
2025-07-24 7:54 ` [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b Krzysztof Kozlowski
2025-08-05 18:18 ` Donald Shannon
2025-08-06 6:12 ` Krzysztof Kozlowski
2025-07-25 3:19 ` Rob Herring (Arm)
2025-07-25 3:25 ` Rob Herring
2025-07-31 2:11 ` Andrew Jeffery [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=2de9da0e95d3e1284a29170c99f7b69baadb9518.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=donalds@nvidia.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@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).