From: Thomas Gleixner <tglx@linutronix.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: Re: [tip:WIP.timers/core 49/68] include/linux/sched/types.h:16:2: error: unknown type name 'u64'
Date: Tue, 20 Aug 2019 00:43:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908200042280.4008@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1908200008320.4008@nanos.tec.linutronix.de>
On Tue, 20 Aug 2019, Thomas Gleixner wrote:
> On Mon, 19 Aug 2019, Thomas Gleixner wrote:
> > On Tue, 20 Aug 2019, kbuild test robot wrote:
> > >
> > > All errors (new ones prefixed by >>):
> > >
> > > In file included from <command-line>:0:0:
> >
> > Huch? What kind of weird include chain is that?
> >
> > > >> 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;
> > > ^~~
> >
> > All (header) files which include that new header have u64 defined.
>
> And building sparc64 allmodconfig does not expose this odd failure
> here. The build fails for a reason related to this series, but that's not
> caused by that sched/types.h header.
Now it came after fixing the other thing, but that build error is really
weird.
prev parent reply other threads:[~2019-08-19 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 21:09 kbuild test robot
2019-08-19 21:24 ` Thomas Gleixner
2019-08-19 22:11 ` Thomas Gleixner
2019-08-19 22:43 ` Thomas Gleixner [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=alpine.DEB.2.21.1908200042280.4008@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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®