From: "H. Peter Anvin" <hpa@kernel.org>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: traps.c replace #if CONFIG_X86_32 with #ifdef CONFIG_X86_32
Date: Tue, 23 Dec 2008 10:20:37 -0800 [thread overview]
Message-ID: <49512BF5.2010705@kernel.org> (raw)
In-Reply-To: <1230049211.14358.2.camel@jaswinder.satnam>
Jaswinder Singh wrote:
> Impact: cleanup, avoid warning in X86_64
>
> Fixes this warning in X86_64:
> CC arch/x86/kernel/traps.o
> arch/x86/kernel/traps.c:695:5: warning: "CONFIG_X86_32" is not defined
>
> Signed-off-by: Jaswinder Singh <jaswinder@infradead.org>
> ---
> arch/x86/kernel/traps.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
> index d327b53..2c00412 100644
> --- a/arch/x86/kernel/traps.c
> +++ b/arch/x86/kernel/traps.c
> @@ -692,7 +692,7 @@ void math_error(void __user *ip)
>
> err = swd & ~cwd & 0x3f;
>
> -#if CONFIG_X86_32
> +#ifdef CONFIG_X86_32
> if (!err)
> return;
> #endif
Applied to tip:x86/fpu, thanks.
Andi: you might have a perspective on this: in math_error() we bail out
if there is no error on i386, but not on x86-64. I am rather assuming
that is because it simply can't happen on x86-64 (no IRQ 13 bullshit) so
it wasn't necessary?
Thanks,
-hpa
next prev parent reply other threads:[~2008-12-23 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 16:20 Jaswinder Singh
2008-12-23 18:20 ` H. Peter Anvin [this message]
2008-12-23 18:48 ` Andi Kleen
2008-12-23 20:32 ` Chuck Ebbert
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=49512BF5.2010705@kernel.org \
--to=hpa@kernel.org \
--cc=andi@firstfloor.org \
--cc=jaswinder@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®