From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Rob Herring <robh@kernel.org>
Cc: kernel test robot <lkp@intel.com>, Frank Li <Frank.Li@nxp.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [linux-next:master 8419/9801] arch/arm/boot/dts/nxp/imx/imx25-eukrea-mbimxsd25-baseboard.dtb: nand-controller@bb000000 (fsl,imx25-nand): Unevaluated properties are not allowed ('clock-names' was unexpected)
Date: Tue, 31 Mar 2026 17:28:19 +0200 [thread overview]
Message-ID: <87fr5g81d8.fsf@bootlin.com> (raw)
In-Reply-To: <CAL_Jsq+pOUuLPaPzQzGVQ_ENq_-7481cxgArbxdSbrPSVpafJA@mail.gmail.com> (Rob Herring's message of "Tue, 31 Mar 2026 10:16:12 -0500")
>> >>> arch/arm/boot/dts/nxp/imx/imx25-eukrea-mbimxsd25-baseboard.dtb: nand-controller@bb000000 (fsl,imx25-nand): Unevaluated properties are not allowed ('clock-names' was unexpected)
>>
>> I haven't investigated the problem, I believe we do not reference any
>> yaml file to authorize clock-names, there should probably be one (or a
>> manual addition in the -legacy.yaml.
>
> That should surely go in a specific controller schema.
>
>> Can you send another follow-up to tidy this up before the merge window
>> opens?
>
> We're really not close to no warnings on arm32, so I wouldn't worry
> about this one too much.
Ack, thanks for the feedback.
Miquèl
next prev parent reply other threads:[~2026-03-31 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 17:05 [linux-next:master 8419/9801] arch/arm/boot/dts/nxp/imx/imx25-eukrea-mbimxsd25-baseboard.dtb: nand-controller@bb000000 (fsl,imx25-nand): Unevaluated properties are not allowed ('clock-names' was unexpected) kernel test robot
2026-03-31 15:09 ` Miquel Raynal
2026-03-31 15:16 ` Rob Herring
2026-03-31 15:28 ` Miquel Raynal [this message]
2026-04-03 7:53 ` Frank Li
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=87fr5g81d8.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Frank.Li@nxp.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.