From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:rcu/next 33/42] include/linux/rcu_segcblist.h:69:2: error: unknown type name 'atomic_long_t'
Date: Sun, 11 Aug 2019 14:57:15 +0800 [thread overview]
Message-ID: <201908111413.HiOSEKVm%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head: 9b319ecdbf1658a6a1df7f92fc9a71aff7a0a86c
commit: 9f3ca094510499050dbd8cd58677f6fd70b5aa60 [33/42] rcu/nocb: Atomic ->len field in rcu_segcblist structure
config: x86_64-randconfig-a003-201932 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout 9f3ca094510499050dbd8cd58677f6fd70b5aa60
# 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 >>):
In file included from <command-line>:0:0:
>> include/linux/rcu_segcblist.h:69:2: error: unknown type name 'atomic_long_t'
atomic_long_t len;
^~~~~~~~~~~~~
include/linux/rcu_segcblist.h:74:2: error: unknown type name 'u8'
u8 enabled;
^~
include/linux/rcu_segcblist.h:75:2: error: unknown type name 'u8'
u8 offloaded;
^~
vim +/atomic_long_t +69 include/linux/rcu_segcblist.h
63
64 struct rcu_segcblist {
65 struct rcu_head *head;
66 struct rcu_head **tails[RCU_CBLIST_NSEGS];
67 unsigned long gp_seq[RCU_CBLIST_NSEGS];
68 #ifdef CONFIG_RCU_NOCB_CPU
> 69 atomic_long_t len;
70 #else
71 long len;
72 #endif
73 long len_lazy;
74 u8 enabled;
75 u8 offloaded;
76 };
77
---
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: 32498 bytes --]
reply other threads:[~2019-08-11 6:57 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=201908111413.HiOSEKVm%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).