From: kernel test robot <lkp@intel.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [congwang:sch_bpf 2/2] ./usr/include/linux/bpf.h:6233:2: error: unknown type name 'u32'
Date: Mon, 30 Aug 2021 20:00:59 +0800 [thread overview]
Message-ID: <202108302047.G7T85yL6-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
tree: https://github.com/congwang/linux.git sch_bpf
head: 176b121d540694ac8584c553c3d7cbbdbdbdeb72
commit: 176b121d540694ac8584c553c3d7cbbdbdbdeb72 [2/2] net_sched: introduce eBPF based Qdisc
config: x86_64-randconfig-c002-20210830 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/congwang/linux/commit/176b121d540694ac8584c553c3d7cbbdbdbdeb72
git remote add congwang https://github.com/congwang/linux.git
git fetch --no-tags congwang sch_bpf
git checkout 176b121d540694ac8584c553c3d7cbbdbdbdeb72
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:32:
>> ./usr/include/linux/bpf.h:6233:2: error: unknown type name 'u32'
6233 | u32 nr_flows;
| ^~~
./usr/include/linux/bpf.h:6234:2: error: unknown type name 'u32'
6234 | u32 nr_packets;
| ^~~
./usr/include/linux/bpf.h:6237:2: error: unknown type name 'u32'
6237 | u32 classid;
| ^~~
>> ./usr/include/linux/bpf.h:6238:2: error: unknown type name 'u64'
6238 | u64 rank;
| ^~~
./usr/include/linux/bpf.h:6239:2: error: unknown type name 'u64'
6239 | u64 delay;
| ^~~
---
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: 33857 bytes --]
reply other threads:[~2021-08-30 12:02 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=202108302047.G7T85yL6-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®