From: Rob Herring <robh@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Quchaosheng <quchaosheng000406@163.com>,
Vincent Mailhol <mailhol@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 2/3] dt-bindings: net: can: holt,hi311x: Convert to DT schema
Date: Fri, 16 Oct 2026 08:09:50 -0500 [thread overview]
Message-ID: <20261016130950.GF5059-robh@kernel.org> (raw)
In-Reply-To: <179209645876.1181445.17999194781071685440.b4-reply@b4>
On Thu, Oct 15, 2026 at 10:34:18PM +0200, Marc Kleine-Budde wrote:
> Hello Rob,
>
> Quchaosheng says the error that your bot finds comes from the latest
> dt-schema git.
>
> On 2026-09-23 09:38:12+08:00, Quchaosheng wrote:
> > Reproduced. The errors come from a dt-schema change in git, not from the
> > patch.
> >
> > They are all in reserved-memory and the IPs that embed it:
> [...]
> > That commit is not in a release yet. Confirmed on the same tree with no
> > patches applied:
> >
> > dt-schema 2026.6 (PyPI) -> clean
> > dt-schema 2026.9 (tag) -> clean
> > dt-schema git 840a01d -> reproduces the errors above
>
> Can you re-trigger the bot or should Quchaosheng re-spin
> the series?
You can ignore those errors. The main branch is now fixed.
Rob
next prev parent reply other threads:[~2026-10-16 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:22 [PATCH v8 0/3] dt-bindings: net: can: convert three bindings to DT schema Quchaosheng
2026-09-22 10:22 ` [PATCH v8 1/3] dt-bindings: net: can: ifi,canfd-1.0: Convert " Quchaosheng
2026-09-22 10:22 ` [PATCH v8 2/3] dt-bindings: net: can: holt,hi311x: " Quchaosheng
2026-09-22 12:46 ` Rob Herring (Arm)
2026-09-23 1:38 ` Quchaosheng
2026-10-15 20:34 ` Marc Kleine-Budde
2026-10-16 13:09 ` Rob Herring [this message]
2026-09-22 10:22 ` [PATCH v8 3/3] dt-bindings: net: can: fsl,mpc5xxx-mscan: " Quchaosheng
2026-09-23 14:30 ` Rob Herring
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=20261016130950.GF5059-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=quchaosheng000406@163.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