mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Peter Yin <peteryin.openbmc@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org,  linux-kernel@vger.kernel.org,
	Joel Stanley <joel@jms.id.au>,
	 devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Andrew Jeffery <andrew@codeconstruct.com.au>
Subject: Re: [PATCH v2 0/2] Revise Meta(Facebook) Harma BMC(AST2600)
Date: Fri, 22 Aug 2025 08:39:47 -0500	[thread overview]
Message-ID: <175586978615.3467242.392732396361998421.robh@kernel.org> (raw)
In-Reply-To: <20250822061454.2610386-1-peteryin.openbmc@gmail.com>


On Fri, 22 Aug 2025 14:14:50 +0800, Peter Yin wrote:
> Summary:
> Revise linux device tree entry related to Meta(Facebook) Harma
> specific devices connected to BMC(AST2600) SoC.
> 
> commit-id: 2236141ed3d6f31f53147c26208dafef6051ae43
> 
> v1 -> v2
>   - Patch 0002 - add power-12v-memory-good
> 
> v1
>   - Patch 0001 - add power monitor support
>   - Patch 0002 - revise gpio name
> 
> Peter Yin (2):
>   ARM: dts: aspeed: harma: add power monitor support
>   ARM: dts: aspeed: harma: revise gpio name
> 
>  .../dts/aspeed/aspeed-bmc-facebook-harma.dts  | 27 ++++++++++++-------
>  1 file changed, 18 insertions(+), 9 deletions(-)
> 
> --
> 2.43.0
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: tags/v6.17-rc1-14-g326d25198112 (exact match)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/aspeed/' for 20250822061454.2610386-1-peteryin.openbmc@gmail.com:

arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dtb: /ahb/apb/display@1e6e6000: failed to match any schema with compatible: ['aspeed,ast2600-gfx', 'syscon']






  parent reply	other threads:[~2025-08-22 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22  6:14 Peter Yin
2025-08-22  6:14 ` [PATCH v2 1/2] ARM: dts: aspeed: harma: add power monitor support Peter Yin
2025-08-22  6:14 ` [PATCH v2 2/2] ARM: dts: aspeed: harma: revise gpio name Peter Yin
2025-08-22 13:39 ` Rob Herring (Arm) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-30  9:21 [PATCH v2 0/2] Revise Meta(Facebook) Harma BMC(AST2600) Peter Yin

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=175586978615.3467242.392732396361998421.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=peteryin.openbmc@gmail.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

all inboxes | Powered by JetHome®