From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 headers: include linux/types.h
Date: Fri, 13 Feb 2009 19:55:00 +0100 [thread overview]
Message-ID: <20090213185500.GA2186@elte.hu> (raw)
In-Reply-To: <4995C157.9020102@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Ingo Molnar wrote:
>> From 56cefcea7c8769ffc04a5609e6ac849e36685468 Mon Sep 17 00:00:00 2001
>> From: Ingo Molnar <mingo@elte.hu>
>> Date: Fri, 13 Feb 2009 13:23:02 +0100
>> Subject: [PATCH] x86 headers: include linux/types.h
>>
>> To properly pick up types relied on by prototypes like 'bool'.
>
> linux/types.h is not assembler-safe.
it is in tip:master, due to:
0fb807c: unconditionally include asm/types.h from linux/types.h
527bdfe: make linux/types.h as assembly safe
Ingo
next prev parent reply other threads:[~2009-02-13 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 23:23 [GIT PULL] clean header untangling Jeremy Fitzhardinge
2009-02-13 12:02 ` Ingo Molnar
2009-02-13 12:18 ` [PATCH] x86 headers: remove duplicate pud_large() definition Ingo Molnar
2009-02-13 12:23 ` [PATCH] x86 headers: include linux/types.h Ingo Molnar
2009-02-13 12:27 ` Ingo Molnar
2009-02-13 12:37 ` [PATCH] x86 headers: protect page_32.h via __ASSEMBLY__ Ingo Molnar
2009-02-13 18:44 ` Jeremy Fitzhardinge
2009-02-13 18:49 ` Ingo Molnar
2009-02-13 18:52 ` Jeremy Fitzhardinge
2009-02-13 18:57 ` Ingo Molnar
2009-02-13 16:25 ` [PATCH] x86 headers: include linux/types.h Jeremy Fitzhardinge
2009-02-13 18:09 ` Ingo Molnar
2009-02-16 21:00 ` Jeremy Fitzhardinge
2009-02-13 18:52 ` Jeremy Fitzhardinge
2009-02-13 18:55 ` Ingo Molnar [this message]
2009-02-13 18:59 ` Jeremy Fitzhardinge
2009-02-13 20:05 ` Ingo Molnar
2009-02-13 18:57 ` Jaswinder Singh Rajput
2009-02-13 16:27 ` [PATCH] x86 headers: remove duplicate pud_large() definition Jeremy Fitzhardinge
2009-02-13 18:02 ` Ingo Molnar
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=20090213185500.GA2186@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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