From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] loongarch: boot: dts: Add Loongson-2K0300 support
Date: Sun, 22 Mar 2026 18:38:13 +0100 [thread overview]
Message-ID: <202603221812.paxyhoFM-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: <tencent_043BCD1F1043957E96ED022D75601AF05505@qq.com>
References: <tencent_043BCD1F1043957E96ED022D75601AF05505@qq.com>
TO: wjjsn <wjjsn@qq.com>
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: chenhuacai@kernel.org
CC: kernel@xen0n.name
CC: devicetree@vger.kernel.org
CC: loongarch@lists.linux.dev
CC: linux-kernel@vger.kernel.org
CC: wjjsn <wjjsn@qq.com>
Hi wjjsn,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v7.0-rc4 next-20260320]
[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/wjjsn/loongarch-boot-dts-Add-Loongson-2K0300-support/20260322-130435
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/tencent_043BCD1F1043957E96ED022D75601AF05505%40qq.com
patch subject: [PATCH] loongarch: boot: dts: Add Loongson-2K0300 support
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: loongarch-randconfig-2051-20260322 (https://download.01.org/0day-ci/archive/20260322/202603221812.paxyhoFM-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
dtschema: 2025.13.dev8+g0515abdd9
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260322/202603221812.paxyhoFM-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/202603221812.paxyhoFM-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/loongarch/boot/dts/loongson-2k0300-ref.dtb: /: failed to match any schema with compatible: ['loongson,ls2k0300-ref', 'loongson,ls2k0300']
>> arch/loongarch/boot/dts/loongson-2k0300-ref.dtb: /: failed to match any schema with compatible: ['loongson,ls2k0300-ref', 'loongson,ls2k0300']
>> arch/loongarch/boot/dts/loongson-2k0300-ref.dtb: clock-controller@16000400 (loongson,ls2k0300-clk): False schema does not allow ['ref_120m']
from schema $id: http://devicetree.org/schemas/clock/loongson,ls2k-clk.yaml
>> arch/loongarch/boot/dts/loongson-2k0300-ref.dtb: clock-controller@16000400 (loongson,ls2k0300-clk): clock-names:0: 'ref_100m' was expected
from schema $id: http://devicetree.org/schemas/clock/loongson,ls2k-clk.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-22 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 17:38 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-22 4:54 [PATCH] loongarch: boot: dts: Add Loongson-2K0300 support wjjsn
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=202603221812.paxyhoFM-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.