From: kbuild test robot <lkp@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: kbuild-all@lists.01.org,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 12485/12912] cc1: error: arch/um/include/uapi: No such file or directory
Date: Wed, 27 May 2020 20:02:15 +0800 [thread overview]
Message-ID: <202005272012.4IvWDLWv%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b0523c7b1c9d0edcd6c0fe6d2cb558a9ad5c60a8
commit: cb6c014b5a3f9082ef4ff45684d7bf17e5441b36 [12485/12912] lib: make a test module with set/clear bit
config: um-allmodconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout cb6c014b5a3f9082ef4ff45684d7bf17e5441b36
# save the attached .config to linux build tree
make W=1 ARCH=um
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> cc1: error: arch/um/include/uapi: No such file or directory [-Werror=missing-include-dirs]
cc1: all warnings being treated as errors
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 22573 bytes --]
next reply other threads:[~2020-05-27 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 12:02 kbuild test robot [this message]
2020-05-27 22:00 ` [linux-next:master 12485/12912] cc1: error: arch/um/include/uapi: No such file or directory Andrew Morton
2020-05-28 1:37 ` [kbuild-all] " Philip Li
2020-06-05 4:26 ` Li Zhijian
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=202005272012.4IvWDLWv%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).