linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo2@yeah.net>
To: Marek Vasut <marex@denx.de>
Cc: kernel test robot <lkp@intel.com>,
	oe-kbuild-all@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [shawnguo:imx/dt64 27/42] arch/arm64/boot/dts/freescale/imx8mp-dhcom-pdk2.dtb: hdmi@32fd8000: Unevaluated properties are not allowed ('ddc-i2c-bus' was unexpected)
Date: Thu, 20 Jun 2024 10:38:48 +0800	[thread overview]
Message-ID: <ZnOWOEBClPpPpraw@dragon> (raw)
In-Reply-To: <70b097d9-f859-4f57-91d2-4053ed9b1717@denx.de>

On Mon, Jun 17, 2024 at 06:41:26AM +0200, Marek Vasut wrote:
> On 6/17/24 5:20 AM, Shawn Guo wrote:
> > Hi Marek,
> 
> Hi,
> 
> > Should I drop the patch or is it bindings that need to be updated?
> 
> It is this bindings patch that fixes the warning:
> 
> [PATCH v2] dt-bindings: display: synopsys,dw-hdmi: Document ddc-i2c-bus in
> core
> 
> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240515062753.111746-1-marex@denx.de/
> 
> No need to drop this patch.
> 
> I can pull the bindings patch in via drm-misc in parallel , is that OK with
> you ?

OK, I'm good as long as we are addressing it.  Thanks!

Shawn



  reply	other threads:[~2024-06-20  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  3:04 [shawnguo:imx/dt64 27/42] arch/arm64/boot/dts/freescale/imx8mp-dhcom-pdk2.dtb: hdmi@32fd8000: Unevaluated properties are not allowed ('ddc-i2c-bus' was unexpected) kernel test robot
2024-06-17  3:20 ` Shawn Guo
2024-06-17  4:41   ` Marek Vasut
2024-06-20  2:38     ` Shawn Guo [this message]
2024-06-20 21:34       ` Marek Vasut

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=ZnOWOEBClPpPpraw@dragon \
    --to=shawnguo2@yeah.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=marex@denx.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shawnguo@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).