From: kbuild test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.timers/core 49/68] include/linux/sched/types.h:16:2: error: unknown type name 'u64'
Date: Tue, 20 Aug 2019 05:09:22 +0800 [thread overview]
Message-ID: <201908200518.CGnq3sBO%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git WIP.timers/core
head: b16101077c4444bc7e0dde91e7ffb258ce1f979b
commit: 83083078874a3b1b29b8171714455b469a17b8ab [49/68] sched: Move struct task_cputime to types.h
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 83083078874a3b1b29b8171714455b469a17b8ab
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64
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/sched/types.h:16:2: error: unknown type name 'u64'
u64 utime;
^~~
include/linux/sched/types.h:17:2: error: unknown type name 'u64'
u64 stime;
^~~
vim +/u64 +16 include/linux/sched/types.h
4
5 /**
6 * struct task_cputime - collected CPU time counts
7 * @utime: time spent in user mode, in nanoseconds
8 * @stime: time spent in kernel mode, in nanoseconds
9 * @sum_exec_runtime: total time spent on the CPU, in nanoseconds
10 *
11 * This structure groups together three kinds of CPU time that are tracked for
12 * threads and thread groups. Most things considering CPU time want to group
13 * these counts together and treat all three of them in parallel.
14 */
15 struct task_cputime {
> 16 u64 utime;
17 u64 stime;
18 unsigned long long sum_exec_runtime;
19 };
20
---
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: 58647 bytes --]
next reply other threads:[~2019-08-19 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 21:09 kbuild test robot [this message]
2019-08-19 21:24 ` Thomas Gleixner
2019-08-19 22:11 ` Thomas Gleixner
2019-08-19 22:43 ` Thomas Gleixner
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=201908200518.CGnq3sBO%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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®