From: kbuild test robot <lkp@intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: 4.17-ad1: -march=native support or Kernel Ricers wanted
Date: Fri, 8 Jun 2018 13:13:27 +0800 [thread overview]
Message-ID: <201806081359.IRzn2BdW%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180604212646.GA10078@avx2>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Hi Alexey,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17]
[cannot apply to tip/x86/core next-20180607]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Alexey-Dobriyan/4-17-ad1-march-native-support-or-Kernel-Ricers-wanted/20180605-090623
config: x86_64-kexec (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
make[3]: execvp: scripts/march-native.sh: Permission denied
make[3]: *** [syncconfig] Error 127
make[2]: *** [syncconfig] Error 2
>> make[1]: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'.
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26167 bytes --]
next prev parent reply other threads:[~2018-06-08 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 21:26 Alexey Dobriyan
2018-06-08 5:13 ` kbuild test robot [this message]
2018-06-08 6:34 ` kbuild test robot
2018-06-08 16:54 ` Alexey Dobriyan
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=201806081359.IRzn2BdW%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=adobriyan@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
/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®