From: Florian Fainelli <f.fainelli@gmail.com>
To: kernel test robot <lkp@intel.com>,
William Zhang <william.zhang@broadcom.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [broadcom-stblinux:devicetree/next 15/23] make[2]: *** No rule to make target 'arch/arm/boot/dts/bcm96855.dtb', needed by '__build'.
Date: Tue, 14 Jun 2022 09:10:26 -0700 [thread overview]
Message-ID: <29fb688b-58a3-be66-3bab-3f8186396c6f@gmail.com> (raw)
In-Reply-To: <202206141752.IB5xCdXS-lkp@intel.com>
On 6/14/22 02:32, kernel test robot wrote:
> tree: https://github.com/Broadcom/stblinux devicetree/next
> head: edb052f67bb9f245f9717b3c11b21022a02fae87
> commit: d2d847e696389916239c5521ca533261d0c0026f [15/23] ARM: dts: Add DTS files for bcmbca SoC BCM6855
> config: arm-randconfig-r035-20220613 (https://download.01.org/0day-ci/archive/20220614/202206141752.IB5xCdXS-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 11.3.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/Broadcom/stblinux/commit/d2d847e696389916239c5521ca533261d0c0026f
> git remote add broadcom-stblinux https://github.com/Broadcom/stblinux
> git fetch --no-tags broadcom-stblinux devicetree/next
> git checkout d2d847e696389916239c5521ca533261d0c0026f
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm 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[2]: *** No rule to make target 'arch/arm/boot/dts/bcm96855.dtb', needed by '__build'.
> make[2]: Target '__build' not remade because of errors.
Now fixed in place.
--
Florian
prev parent reply other threads:[~2022-06-14 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:32 kernel test robot
2022-06-14 16:10 ` Florian Fainelli [this message]
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=29fb688b-58a3-be66-3bab-3f8186396c6f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=william.zhang@broadcom.com \
/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®