From: kbuild test robot <lkp@intel.com>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: kbuild-all@01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm:cex7 21/21] drivers/bus/fsl-mc/fsl-mc-uapi.c:14:10: fatal error: uapi/linux/fsl_mc.h: No such file or directory
Date: Mon, 16 Sep 2019 07:09:25 +0800 [thread overview]
Message-ID: <201909160723.jMYkYPyX%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
tree: git://git.armlinux.org.uk/~rmk/linux-arm.git cex7
head: ea40d247d6cf45a3b72960cc3bd9b9db691f404a
commit: ea40d247d6cf45a3b72960cc3bd9b9db691f404a [21/21] fsl-mc: add uapi interface for restool
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
reproduce:
git checkout ea40d247d6cf45a3b72960cc3bd9b9db691f404a
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/bus/fsl-mc/fsl-mc-uapi.c:14:10: fatal error: uapi/linux/fsl_mc.h: No such file or directory
#include <uapi/linux/fsl_mc.h>
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +14 drivers/bus/fsl-mc/fsl-mc-uapi.c
> 14 #include <uapi/linux/fsl_mc.h>
15 #undef fsl_mc_command
16
---
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: 68833 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-09-15 23:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201909160723.jMYkYPyX%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.