0 day kernel build service
 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: leds: lacie,ns2-leds: Convert to DT schema
Date: Thu, 23 Jul 2026 15:37:53 +0200	[thread overview]
Message-ID: <202607231542.6ovJrInT-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: <20260721192754.46344-1-ninadnaik07@gmail.com>
References: <20260721192754.46344-1-ninadnaik07@gmail.com>
TO: Ninad Naik <ninadnaik07@gmail.com>
TO: lee@kernel.org
TO: pavel@kernel.org
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: simon.guinot@sequanux.org
CC: linux-leds@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: me@brighamcampbell.com
CC: linux-kernel-mentees@lists.linux.dev
CC: skhan@linuxfoundation.org
CC: Ninad Naik <ninadnaik07@gmail.com>

Hi Ninad,

kernel test robot noticed the following build warnings:

[auto build test WARNING on lee-leds/for-leds-next]
[also build test WARNING on linus/master v7.2-rc4 next-20260722]
[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/Ninad-Naik/dt-bindings-leds-lacie-ns2-leds-Convert-to-DT-schema/20260722-040054
base:   https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
patch link:    https://lore.kernel.org/r/20260721192754.46344-1-ninadnaik07%40gmail.com
patch subject: [PATCH v2] dt-bindings: leds: lacie,ns2-leds: Convert to DT schema
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: arm-randconfig-2053-20260722 (https://download.01.org/0day-ci/archive/20260723/202607231542.6ovJrInT-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 16.1.0
dtschema: 2026.7.dev1+g2203c1720
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260723/202607231542.6ovJrInT-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/202607231542.6ovJrInT-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: mvsdio@d4000 (marvell,orion-sdio): $nodename:0: 'mvsdio@d4000' does not match '^mmc(@.*)?$'
   	from schema $id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/system-controller@18200: failed to match any schema with compatible: ['marvell,armada-370-xp-system-controller']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/cpu-config@21000: failed to match any schema with compatible: ['marvell,armada-370-cpu-config']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/internal-regs/audio-controller@30000: failed to match any schema with compatible: ['marvell,armada370-audio']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: /soc/bootrom: failed to match any schema with compatible: ['marvell,bootrom']
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: sa-sram (mmio-sram): 'reg-names' does not match any of the regexes: '^([a-z0-9]+-)*sram(-section)?@[a-f0-9]+$', '^pinctrl-[0-9]+$'
   	from schema $id: http://devicetree.org/schemas/sram/sram.yaml
   arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: sa-sram (mmio-sram): $nodename:0: 'sa-sram' does not match '^sram(@.*)?'
   	from schema $id: http://devicetree.org/schemas/sram/sram.yaml
>> arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: leds-ns2 (lacie,ns2-leds): white-sata2: Unevaluated properties are not allowed ('num-modes' was unexpected)
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml
>> arch/arm/boot/dts/marvell/armada-370-seagate-nas-4bay.dtb: leds-ns2 (lacie,ns2-leds): white-sata3: Unevaluated properties are not allowed ('num-modes' was unexpected)
   	from schema $id: http://devicetree.org/schemas/leds/lacie,ns2-leds.yaml

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

                 reply	other threads:[~2026-07-23 13:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202607231542.6ovJrInT-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox