From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [qcom:arm64-for-7.2 77/90] arch/arm64/boot/dts/qcom/ipq9650-rdp488.dtb: /soc@0/pinctrl@1000000: failed to match any schema with compatible: ['qcom,ipq9650-tlmm']
Date: Thu, 14 May 2026 23:30:15 +0200 [thread overview]
Message-ID: <202605142335.eRlXRXoY-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
TO: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
CC: Bjorn Andersson <andersson@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux arm64-for-7.2
head: c4b423835ee7529854ab39b50cf766bc4c6b4d66
commit: 8cef25a0044d3e7caef56a43bf316336fe39b5d8 [77/90] arm64: dts: qcom: add IPQ9650 SoC and rdp488 board support
:::::: branch date: 2 days ago
:::::: commit date: 3 days ago
config: arm64-randconfig-2055-20260514 (https://download.01.org/0day-ci/archive/20260514/202605142335.eRlXRXoY-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
dtschema: 2026.5.dev9+gdf9ad30c5
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605142335.eRlXRXoY-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/202605142335.eRlXRXoY-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/arm64/boot/dts/qcom/ipq9650-rdp488.dtb: /soc@0/pinctrl@1000000: failed to match any schema with compatible: ['qcom,ipq9650-tlmm']
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-14 21:31 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=202605142335.eRlXRXoY-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.