From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] dt-bindings: usb: Add Socionext Uniphier DWC3 controller
Date: Wed, 24 Dec 2025 12:45:41 +0100 [thread overview]
Message-ID: <202512241211.t8uGeVRw-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: <20251215212507.3317805-1-robh@kernel.org>
References: <20251215212507.3317805-1-robh@kernel.org>
TO: "Rob Herring (Arm)" <robh@kernel.org>
TO: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
TO: Krzysztof Kozlowski <krzk@kernel.org>
TO: Conor Dooley <conor+dt@kernel.org>
TO: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
TO: Masami Hiramatsu <mhiramat@kernel.org>
CC: linux-usb@vger.kernel.org
CC: devicetree@vger.kernel.org
CC: linux-arm-kernel@lists.infradead.org
CC: linux-kernel@vger.kernel.org
Hi Rob,
kernel test robot noticed the following build warnings:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on usb/usb-next usb/usb-linus westeri-thunderbolt/next krzk-dt/for-next linus/master v6.16-rc1 next-20251219]
[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-usb-Add-Socionext-Uniphier-DWC3-controller/20251216-053102
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
patch link: https://lore.kernel.org/r/20251215212507.3317805-1-robh%40kernel.org
patch subject: [PATCH] dt-bindings: usb: Add Socionext Uniphier DWC3 controller
:::::: branch date: 9 days ago
:::::: commit date: 9 days ago
config: arm-randconfig-2051-20251217 (https://download.01.org/0day-ci/archive/20251224/202512241211.t8uGeVRw-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
dtschema version: 2025.12
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512241211.t8uGeVRw-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/202512241211.t8uGeVRw-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
arch/arm/boot/dts/socionext/uniphier-pro4-ace.dtb: /soc/smpctrl@59801000: failed to match any schema with compatible: ['socionext,uniphier-smpctrl']
>> arch/arm/boot/dts/socionext/uniphier-pro4-ace.dtb: usb@65c00000 (socionext,uniphier-dwc3): phys: [[48]] is too short
from schema $id: http://devicetree.org/schemas/usb/socionext,uniphier-dwc3.yaml
--
arch/arm/boot/dts/socionext/uniphier-pro4-ref.dtb: /soc/smpctrl@59801000: failed to match any schema with compatible: ['socionext,uniphier-smpctrl']
>> arch/arm/boot/dts/socionext/uniphier-pro4-ref.dtb: usb@65c00000 (socionext,uniphier-dwc3): phys: [[49]] is too short
from schema $id: http://devicetree.org/schemas/usb/socionext,uniphier-dwc3.yaml
--
arch/arm/boot/dts/socionext/uniphier-pro4-sanji.dtb: /soc/smpctrl@59801000: failed to match any schema with compatible: ['socionext,uniphier-smpctrl']
>> arch/arm/boot/dts/socionext/uniphier-pro4-sanji.dtb: usb@65c00000 (socionext,uniphier-dwc3): phys: [[48]] is too short
from schema $id: http://devicetree.org/schemas/usb/socionext,uniphier-dwc3.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-24 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 11:45 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-15 21:25 [PATCH] dt-bindings: usb: Add Socionext Uniphier DWC3 controller Rob Herring (Arm)
2025-12-16 1:20 ` Kunihiko Hayashi
2025-12-16 16:38 ` Rob Herring
2025-12-18 9:52 ` Kunihiko Hayashi
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=202512241211.t8uGeVRw-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.