From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] dt-bindings: rtc: moxa,moxart-rtc: convert to json-schema
Date: Tue, 31 Mar 2026 23:35:59 +0200 [thread overview]
Message-ID: <202603312318.dkRDIuom-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: <20260329184615.454887-1-robyserbanpascu06@gmail.com>
References: <20260329184615.454887-1-robyserbanpascu06@gmail.com>
TO: "Serban-Pascu Robert" <robyserbanpascu06@gmail.com>
TO: alexandre.belloni@bootlin.com
CC: robh@kernel.org
CC: krzk+dt@kernel.org
CC: conor+dt@kernel.org
CC: devicetree@vger.kernel.org
CC: linux-rtc@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: daniel.baluta@nxp.com
CC: "Serban-Pascu Robert" <robyserbanpascu06@gmail.com>
Hi Serban-Pascu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on abelloni/rtc-next]
[also build test WARNING on robh/for-next linus/master v7.0-rc6 next-20260330]
[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/Serban-Pascu-Robert/dt-bindings-rtc-moxa-moxart-rtc-convert-to-json-schema/20260330-111814
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
patch link: https://lore.kernel.org/r/20260329184615.454887-1-robyserbanpascu06%40gmail.com
patch subject: [PATCH] dt-bindings: rtc: moxa,moxart-rtc: convert to json-schema
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: arm-randconfig-2052-20260330 (https://download.01.org/0day-ci/archive/20260331/202603312318.dkRDIuom-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
dtschema: 2025.13.dev9+g4cd3cdfac
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260331/202603312318.dkRDIuom-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/202603312318.dkRDIuom-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: interrupt-controller@98800000 (moxa,moxart-ic): 'interrupt-mask' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/interrupt-controller/faraday,ftintc010.yaml
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: gpio@98700000 (moxa,moxart-gpio): 'oneOf' conditional failed, one must be fixed:
'interrupts' is a required property
'interrupts-extended' is a required property
from schema $id: http://devicetree.org/schemas/gpio/faraday,ftgpio010.yaml
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: gpio@98700000 (moxa,moxart-gpio): 'interrupt-controller' is a required property
from schema $id: http://devicetree.org/schemas/gpio/faraday,ftgpio010.yaml
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: gpio@98700000 (moxa,moxart-gpio): '#interrupt-cells' is a required property
from schema $id: http://devicetree.org/schemas/gpio/faraday,ftgpio010.yaml
>> arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: rtc (moxa,moxart-rtc): 'gpio-rtc-data', 'gpio-rtc-reset', 'gpio-rtc-sclk' do not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/rtc/moxa,moxart-rtc.yaml
>> arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: rtc (moxa,moxart-rtc): 'rtc-sclk-gpios' is a required property
from schema $id: http://devicetree.org/schemas/rtc/moxa,moxart-rtc.yaml
>> arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: rtc (moxa,moxart-rtc): 'rtc-data-gpios' is a required property
from schema $id: http://devicetree.org/schemas/rtc/moxa,moxart-rtc.yaml
>> arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: rtc (moxa,moxart-rtc): 'rtc-reset-gpios' is a required property
from schema $id: http://devicetree.org/schemas/rtc/moxa,moxart-rtc.yaml
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: /soc/dma@90500000: failed to match any schema with compatible: ['moxa,moxart-dma']
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: /soc/mmc@98e00000: failed to match any schema with compatible: ['moxa,moxart-mmc']
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: /soc/mdio@90900090: failed to match any schema with compatible: ['moxa,moxart-mdio']
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: /soc/mdio@90900090/ethernet-phy@1: failed to match any schema with compatible: ['moxa,moxart-rtl8201cp', 'ethernet-phy-ieee802.3-c22']
arch/arm/boot/dts/moxa/moxart-uc7112lx.dtb: ethernet-phy@1 (moxa,moxart-rtl8201cp): compatible: 'oneOf' conditional failed, one must be fixed:
['moxa,moxart-rtl8201cp', 'ethernet-phy-ieee802.3-c22'] is too long
'ethernet-phy-ieee802.3-c22' was expected
'ethernet-phy-ieee802.3-c45' was expected
'moxa,moxart-rtl8201cp' does not match '^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-31 21:36 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=202603312318.dkRDIuom-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