All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2] dt-bindings: Fix phandle-array constraints, again
Date: Sat, 16 May 2026 21:13:17 +0200	[thread overview]
Message-ID: <202605162124.kke51ExO-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260507201749.2605365-1-robh@kernel.org>
References: <20260507201749.2605365-1-robh@kernel.org>
TO: "Rob Herring (Arm)" <robh@kernel.org>
TO: Maxime Ripard <mripard@kernel.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Wolfram Sang <wsa-dev@sang-engineering.com>
TO: Andi Shyti <andi.shyti@kernel.org>
TO: Ulf Hansson <ulfh@kernel.org>
TO: Andrew Lunn <andrew+netdev@lunn.ch>
TO: "David S. Miller" <davem@davemloft.net>
CC: netdev@vger.kernel.org
TO: Eric Dumazet <edumazet@google.com>
TO: Jakub Kicinski <kuba@kernel.org>
TO: Paolo Abeni <pabeni@redhat.com>
TO: Johannes Berg <johannes@sipsolutions.net>
TO: Jeff Johnson <jjohnson@kernel.org>
TO: Bjorn Helgaas <helgaas@kernel.org>
TO: Lorenzo Pieralisi <lpieralisi@kernel.org>
TO: "Krzysztof Wilczyński" <kwilczynski@kernel.org>
TO: Manivannan Sadhasivam <mani@kernel.org>
TO: Bjorn Andersson <andersson@kernel.org>
TO: Mathieu Poirier <mathieu.poirier@linaro.org>
TO: Sylwester Nawrocki <s.nawrocki@samsung.com>
TO: Mark Brown <broonie@kernel.org>
TO: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
CC: dri-devel@lists.freedesktop.org
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-kernel@vger.kernel.org
CC: linux-i2c@vger.kernel.org
CC: linux-mmc@vger.kernel.org
CC: linux-wireless@vger.kernel.org

Hi Rob,

kernel test robot noticed the following build warnings:

[auto build test WARNING on remoteproc/rproc-next]
[also build test WARNING on robh/for-next wireless-next/main wireless/main next-20260508]
[cannot apply to linus/master v6.16-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Rob-Herring-Arm/dt-bindings-Fix-phandle-array-constraints-again/20260513-145940
base:   https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git rproc-next
patch link:    https://lore.kernel.org/r/20260507201749.2605365-1-robh%40kernel.org
patch subject: [PATCH v2] dt-bindings: Fix phandle-array constraints, again
:::::: branch date: 4 days ago
:::::: commit date: 4 days ago
config: arm-randconfig-2054-20260513 (https://download.01.org/0day-ci/archive/20260516/202605162124.kke51ExO-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
dtschema: 2026.5.dev9+gdf9ad30c5
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605162124.kke51ExO-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202605162124.kke51ExO-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
   arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [99, 100] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[99, 100]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
   arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux4 (i2c-demux-pinctrl): i2c-parent:0: [115, 116] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux4 (i2c-demux-pinctrl): i2c-parent: [[115, 116]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
--
   arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [83, 84] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[83, 84]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
   arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent:0: [85, 86] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent: [[85, 86]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
   arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux3 (i2c-demux-pinctrl): i2c-parent:0: [98, 99] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7791-koelsch.dtb: i2c-mux3 (i2c-demux-pinctrl): i2c-parent: [[98, 99]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
--
   arch/arm/boot/dts/renesas/r8a7791-porter.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [63, 64] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7791-porter.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[63, 64]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
--
   arch/arm/boot/dts/renesas/r8a7793-gose.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [74, 75] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7793-gose.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[74, 75]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
   arch/arm/boot/dts/renesas/r8a7793-gose.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent:0: [86, 87] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7793-gose.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent: [[86, 87]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
--
   arch/arm/boot/dts/renesas/r8a7794-alt.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [56, 57] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7794-alt.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[56, 57]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
   arch/arm/boot/dts/renesas/r8a7794-alt.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent:0: [59, 60] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7794-alt.dtb: i2c-mux2 (i2c-demux-pinctrl): i2c-parent: [[59, 60]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
--
   arch/arm/boot/dts/renesas/r8a7794-silk.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [61, 62] is too long
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
>> arch/arm/boot/dts/renesas/r8a7794-silk.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[61, 62]] is too short
   	from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-05-16 19:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 19:13 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-07 20:16 [PATCH v2] dt-bindings: Fix phandle-array constraints, again Rob Herring (Arm)
2026-05-07 21:30 ` Rob Herring (Arm)
2026-05-08 13:20   ` Rob Herring
2026-05-08 20:19 ` sashiko-bot
2026-05-19 13:27 ` Manivannan Sadhasivam

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=202605162124.kke51ExO-lkp@intel.com \
    --to=lkp@intel.com \
    --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 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.