From: Andi Kleen <andi@firstfloor.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Use more gcc extensions in the Linux headers
Date: 09 Mar 2007 17:52:00 +0100 [thread overview]
Message-ID: <p733b4ebbrj.fsf@bingen.suse.de> (raw)
In-Reply-To: <1173419792.32234.131.camel@localhost.localdomain>
Rusty Russell <rusty@rustcorp.com.au> writes:
> __builtin_types_compatible_p() has been around since gcc 2.95, and we
> don't use it anywhere. This patch quietly fixes that.
Using BUILD_BUG_ON_ZERO() would have been somewhat cleaner.
-Andi
next prev parent reply other threads:[~2007-03-09 15:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 5:56 [PATCH] Use more gcc extensions in the Linux headers Rusty Russell
2007-03-09 6:22 ` Stephen Rothwell
2007-03-09 6:35 ` Linus Torvalds
2007-03-09 6:50 ` Andrey Panin
2007-03-09 7:53 ` Christoph Hellwig
2007-03-09 9:02 ` Andrey Panin
2007-03-09 9:05 ` Christoph Hellwig
2007-03-09 17:47 ` Linus Torvalds
2007-03-10 20:36 ` Trent Piepho
2007-03-09 7:52 ` Christoph Hellwig
2007-03-09 8:35 ` Jarek Poplawski
2007-03-09 11:27 ` Theodore Ts'o
2007-03-09 16:52 ` Andi Kleen [this message]
2007-03-09 22:57 ` Rusty Russell
2007-03-09 23:02 ` Randy Dunlap
2007-03-09 23:09 ` Robert P. J. Day
2007-03-09 23:12 ` Roland Dreier
2007-03-10 1:04 ` Jan Engelhardt
2007-03-11 2:50 ` Rusty Russell
2007-03-11 2:58 ` Jan Engelhardt
2007-03-11 3:19 ` Rusty Russell
2007-03-11 21:40 ` Valdis.Kletnieks
2007-03-10 4:03 ` Valdis.Kletnieks
2007-03-10 4:24 ` Randy Dunlap
2007-03-11 15:56 ` Valdis.Kletnieks
2007-03-10 5:19 ` Nigel Cunningham
2007-03-10 14:01 ` Jan Engelhardt
2007-03-10 15:18 ` Andreas Schwab
2007-03-10 16:53 ` Jan Engelhardt
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=p733b4ebbrj.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.