From: kernel test robot <lkp@intel.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, devicetree@vger.kernel.org
Cc: kbuild-all@lists.01.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2 3/3] arm64: dts: freescale: Add InnoComm i.MX8MM based WB15 SoM and EVK
Date: Thu, 15 Sep 2022 10:47:47 +0800 [thread overview]
Message-ID: <202209151014.DmoRoYFo-lkp@intel.com> (raw)
In-Reply-To: <20220913103337.1849023-4-s.hauer@pengutronix.de>
Hi Sascha,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v6.0-rc5]
[cannot apply to next-20220914]
[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/Sascha-Hauer/arm64-dts-Add-InnoComm-WB15-EVK-support/20220913-183559
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (https://download.01.org/0day-ci/archive/20220915/202209151014.DmoRoYFo-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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/intel-lab-lkp/linux/commit/1d6fe7241418270e6c26852e85104d10141c8678
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Sascha-Hauer/arm64-dts-Add-InnoComm-WB15-EVK-support/20220913-183559
git checkout 1d6fe7241418270e6c26852e85104d10141c8678
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> make[3]: *** No rule to make target 'arch/arm64/boot/dts/freescale/imx8mm-innocom-wb15-evk.dtb', needed by '__build'.
make[3]: Target '__build' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-15 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:33 [PATCH v2 0/3] arm64: dts: Add InnoComm WB15-EVK support Sascha Hauer
2022-09-13 10:33 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add prefix for InnoComm Sascha Hauer
2022-09-14 11:54 ` Rob Herring
2022-09-13 10:33 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Add InnoComm WB15 EVK Sascha Hauer
2022-09-14 11:54 ` Rob Herring
2022-09-13 10:33 ` [PATCH v2 3/3] arm64: dts: freescale: Add InnoComm i.MX8MM based WB15 SoM and EVK Sascha Hauer
2022-09-15 2:47 ` kernel test robot [this message]
2022-09-15 15:21 ` Krzysztof Kozlowski
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=202209151014.DmoRoYFo-lkp@intel.com \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).