From: Vincent Jardin <vjardin@free.fr>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Frank Li <Frank.Li@nxp.com>,
imx@lists.linux.dev
Subject: Re: [frank-li:imx/dt64 65/103] arch/arm64/boot/dts/freescale/fsl-lx2160a-nbxv3.dtb: gpio@2310000 (fsl,ls2080a-gpio): 'pltrst-hog' does not match any of the regexes: '^pinctrl-[0-9]+$'
Date: Tue, 29 Sep 2026 21:48:18 +0200 [thread overview]
Message-ID: <arwWAqkwvlf79z45@L30177.local> (raw)
In-Reply-To: <202609291726.iogWKGg7-lkp@intel.com>
On Tue, Sep 29, 2026 at 05:36:04PM +0200, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git imx/dt64
> head: 8c40f32361d566c0882e9d92abab36256b268291
> commit: 565b6713a460126874d15654fe24d995a57c822b [65/103] arm64: dts: freescale: add Nodebox v3 CPU Module
[...]
> >> arch/arm64/boot/dts/freescale/fsl-lx2160a-nbxv3.dtb: gpio@2310000 (fsl,ls2080a-gpio): 'pltrst-hog' does not match any of the regexes: '^pinctrl-[0-9]+$'
> from schema $id: http://devicetree.org/schemas/gpio/fsl,qoriq-gpio.yaml
It is the dependency mentioned in the cover letter: the gpio-hog child
nodes are allowed by
78c0baf85cd0 ("dt-bindings: gpio: fsl,qoriq-gpio: allow gpio-hog child nodes")
which Bartosz applied to gpio/for-next, not to imx/dt64. The warning goes
away once both trees are merged for v7.4-rc1, so nothing is needed on the
imx side.
Best regards,
Vincent
next parent reply other threads:[~2026-09-29 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202609291726.iogWKGg7-lkp@intel.com>
2026-09-29 19:48 ` Vincent Jardin [this message]
2026-09-30 12:04 ` [frank-li:imx/dt64 65/103] arch/arm64/boot/dts/freescale/fsl-lx2160a-nbxv3.dtb: gpio@2310000 (fsl,ls2080a-gpio): 'pltrst-hog' does not match any of the regexes: '^pinctrl-[0-9]+$' Philip 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=arwWAqkwvlf79z45@L30177.local \
--to=vjardin@free.fr \
--cc=Frank.Li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
/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