From: kernel test robot <lkp@intel.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [nbd168-wireless:mtk-flow-offload 5/14] ERROR: Input tree has errors, aborting (use -f to force output)
Date: Wed, 23 Feb 2022 03:56:23 +0800 [thread overview]
Message-ID: <202202230356.HxgGrXil-lkp@intel.com> (raw)
tree: https://github.com/nbd168/wireless mtk-flow-offload
head: c5c9c022de79aa26f88a358954a868d8bbc2af11
commit: ad070cb96f71f13aa6fde0e13fba0a87c1cc91bf [5/14] arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch
config: arm64-buildonly-randconfig-r001-20220221 (https://download.01.org/0day-ci/archive/20220223/202202230356.HxgGrXil-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/nbd168/wireless/commit/ad070cb96f71f13aa6fde0e13fba0a87c1cc91bf
git remote add nbd168-wireless https://github.com/nbd168/wireless
git fetch --no-tags nbd168-wireless mtk-flow-offload
git checkout ad070cb96f71f13aa6fde0e13fba0a87c1cc91bf
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
also defined at arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts:103.6-174.3
>> ERROR: Input tree has errors, aborting (use -f to force output)
--
also defined at arch/arm64/boot/dts/mediatek/mt7622-bananapi-bpi-r64.dts:117.6-197.3
>> ERROR: Input tree has errors, aborting (use -f to force output)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-22 19:56 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=202202230356.HxgGrXil-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
/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
all inboxes | Powered by JetHome®