From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: Alan Kao <alankao@andestech.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [linux-next:master 10574/11713] scripts/Makefile.clean:15: arch/nds32/Makefile: No such file or directory
Date: Thu, 10 Mar 2022 10:00:59 +0100 [thread overview]
Message-ID: <CAK8P3a2Am6Ks3q-isJKNiqFAJ39+Jq7a+woPoLfkyzMt_WmfiQ@mail.gmail.com> (raw)
In-Reply-To: <202203101509.2EsQ4zK2-lkp@intel.com>
On Thu, Mar 10, 2022 at 8:12 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 4e7a74a6856f8613dab9794da4b5cfb8fd54fb8c
> commit: 3edb65f4e8fdec0569edf6a0e74675d2e5e6fe0e [10574/11713] nds32: Remove the architecture
> config: nds32-randconfig-r035-20220310
> compiler: nds32le-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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3edb65f4e8fdec0569edf6a0e74675d2e5e6fe0e
> 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 3edb65f4e8fdec0569edf6a0e74675d2e5e6fe0e
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=nds32 randconfig
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nds32 distclean
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
nds32 is scheduled for removal now, please drop it from the lkp test
infrastructure
for linux-next/5.17 and higher.
Arnd
next prev parent reply other threads:[~2022-03-10 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 7:12 kernel test robot
2022-03-10 9:00 ` Arnd Bergmann [this message]
2022-03-23 8:14 ` [kbuild-all] " Chen, Rong A
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=CAK8P3a2Am6Ks3q-isJKNiqFAJ39+Jq7a+woPoLfkyzMt_WmfiQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=alankao@andestech.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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