From: Andrew Morton <akpm@linux-foundation.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linux/compiler.h: don't use bool
Date: Fri, 17 Aug 2018 13:39:35 -0700 [thread overview]
Message-ID: <20180817133935.b93ce7534656e587d4c8d3e6@linux-foundation.org> (raw)
In-Reply-To: <20180817101036.20969-1-linux@rasmusvillemoes.dk>
On Fri, 17 Aug 2018 12:10:35 +0200 Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
> Appararently, it's possible to have a non-trivial TU include a few headers,
> including linux/build_bug.h, without ending up with linux/types.h. So
> the 0day bot sent me
What's a "TU"?
>
> config: um-x86_64_defconfig (attached as .config)
>
> >> include/linux/compiler.h:316:3: error: unknown type name 'bool'; did you mean '_Bool'?
> bool __cond = !(condition); \
>
> for something I'm working on.
>
> Rather than contributing to the #include madness and including
> linux/types.h from compiler.h, just use int.
next prev parent reply other threads:[~2018-08-17 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 10:10 [PATCH] linux/compiler.h: don't use bool Rasmus Villemoes
2018-08-17 20:39 ` Andrew Morton [this message]
2018-08-17 20:43 ` Josh Triplett
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=20180817133935.b93ce7534656e587d4c8d3e6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).