Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: soc@kernel.org
Subject: Re: [PATCH v2 resend] ARM: dts: aspeed: Fix pca954x i2c-mux node names
Date: Sat, 12 Aug 2023 12:50:21 +0000	[thread overview]
Message-ID: <169184462197.4542.13604850491003227102.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <11a017bc452503cd391a17df3f029177f3e8e2d8.1689600517.git.geert+renesas@glider.be>

Hello:

This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Mon, 17 Jul 2023 15:30:55 +0200 you wrote:
> "make dtbs_check":
> 
>     arch/arm/boot/dts/aspeed-bmc-bytedance-g220a.dtb: i2c-switch@70: $nodename:0: 'i2c-switch@70' does not match '^(i2c-?)?mux'
> 	    From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
>     arm/boot/dts/aspeed-bmc-bytedance-g220a.dtb: i2c-switch@70: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'i2c@0', 'i2c@1', 'i2c@2', 'i2c@3' were unexpected)
> 	    From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
>     ...
> 
> [...]

Here is the summary with links:
  - [v2,resend] ARM: dts: aspeed: Fix pca954x i2c-mux node names
    https://git.kernel.org/soc/soc/c/4b46d86c978b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-08-12 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 13:30 [PATCH v2 resend] ARM: dts: aspeed: Fix pca954x i2c-mux node names Geert Uytterhoeven
2023-08-12 12:50 ` patchwork-bot+linux-soc [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=169184462197.4542.13604850491003227102.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=soc@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