From: Souptick Joarder <jrdr.linux@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Gabriel Somlo <gsomlo@gmail.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Stafford Horne <shorne@gmail.com>
Subject: Re: [linux-next:master 3035/6048] sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
Date: Thu, 28 Jan 2021 09:35:22 +0530 [thread overview]
Message-ID: <CAFqt6zbK-t6XNofOTKLCVT+X_tiwXHmh9i1E=qvQy-3fqyj-sA@mail.gmail.com> (raw)
In-Reply-To: <202101261118.GbbYSlHu-lkp@intel.com>
On Tue, Jan 26, 2021 at 8:46 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 59fa6a163ffabc1bf25c5e0e33899e268a96d3cc
> commit: 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e [3035/6048] drivers/soc/litex: move generic accessors to litex.h
> config: sh-randconfig-r025-20210125 (attached as .config)
> compiler: sh4-linux-gcc (GCC) 9.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 9d93a9e8aab3f82b6742dd034a6a81d4025cd82e
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=sh
>
> 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 >>):
>
> >> sh4-linux-nm: 'drivers/soc/litex/litex_soc_ctrl.o': No such file
This file exists and required are also enabled.
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-01-28 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 3:15 kernel test robot
2021-01-28 4:05 ` Souptick Joarder [this message]
2021-02-08 6:29 ` Rong Chen
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='CAFqt6zbK-t6XNofOTKLCVT+X_tiwXHmh9i1E=qvQy-3fqyj-sA@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=gsomlo@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=shorne@gmail.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