From: kbuild test robot <lkp@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [iecm/idpf V1 14/14] idpf: Introduce idpf driver
Date: Sat, 16 May 2020 13:31:55 +0800 [thread overview]
Message-ID: <202005161327.KV4UeKpU%lkp@intel.com> (raw)
In-Reply-To: <20200515063500.48301-15-alice.michael@intel.com>
Hi Alice,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on jkirsher-next-queue/dev-queue]
[also build test ERROR on linus/master v5.7-rc5 next-20200515]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Alice-Michael/iecm-idpf-series-cover-letter/20200515-230855
base: https://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git dev-queue
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 9d4cf5bd421fb6467ff5f00e26a37527246dd4d6)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 <<):
In file included from drivers/net/ethernet/intel/idpf/idpf_main.c:8:
>> drivers/net/ethernet/intel/idpf/idpf_dev.h:7:10: fatal error: 'iecm.h' file not found
#include "iecm.h"
^~~~~~~~
1 error generated.
vim +7 drivers/net/ethernet/intel/idpf/idpf_dev.h
6
> 7 #include "iecm.h"
8
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all at lists.01.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 73506 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20200516/234fe3b1/attachment-0001.bin>
prev parent reply other threads:[~2020-05-16 5:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 6:34 [Intel-wired-lan] [iecm/idpf V1 00/14] iecm/idpf series cover letter Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 01/14] iecm: Add framework set of header files Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 02/14] iecm: Add TX/RX " Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 03/14] iecm: Common module introduction and function stubs Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 04/14] iecm: Add basic netdevice functionality Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 05/14] iecm: Implement mailbox functionality Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 06/14] iecm: Implement virtchnl commands Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 07/14] iecm: Implement vector allocation Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 08/14] iecm: Init and allocate vport Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 09/14] iecm: Deinit vport Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 10/14] iecm: Add splitq TX/RX Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 11/14] iecm: Add singleq TX/RX Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 12/14] iecm: Add ethtool Alice Michael
2020-05-15 6:34 ` [Intel-wired-lan] [iecm/idpf V1 13/14] iecm: Add iecm to the kernel build system Alice Michael
2020-05-15 6:35 ` [Intel-wired-lan] [iecm/idpf V1 14/14] idpf: Introduce idpf driver Alice Michael
2020-05-16 5:31 ` kbuild test robot [this message]
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=202005161327.KV4UeKpU%lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-wired-lan@osuosl.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