From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] - UV fix compile error on IA64 & eliminate compiler warning
Date: Thu, 29 Jan 2009 14:33:08 +0100 [thread overview]
Message-ID: <20090129133308.GE24391@elte.hu> (raw)
In-Reply-To: <20090128212104.GA1156@sgi.com>
* Jack Steiner <steiner@sgi.com> wrote:
>
> The GRU driver is used on both IA64 & x86.
> The 2 architectures have different ways of detecting the
> platform type, ie. whether the platform is a UV system.
> Although it is possible to reconcile the 2 methods,
> only one place currently makes the test.
>
> Also eliminate a warning message in uv.h.
>
> Signed-off-by: Jack Steiner <steiner@sgi.com>
>
>
> ---
> arch/x86/include/asm/uv/uv.h | 1 +
> drivers/misc/sgi-gru/gru.h | 2 --
> drivers/misc/sgi-gru/grufile.c | 1 +
> 3 files changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux/arch/x86/include/asm/uv/uv.h
> ===================================================================
> --- linux.orig/arch/x86/include/asm/uv/uv.h 2009-01-28 12:43:27.000000000 -0600
> +++ linux/arch/x86/include/asm/uv/uv.h 2009-01-28 15:13:58.000000000 -0600
> @@ -2,6 +2,7 @@
> #define _ASM_X86_UV_UV_H
>
> enum uv_system_type {UV_NONE, UV_LEGACY_APIC, UV_X2APIC, UV_NON_UNIQUE_APIC};
> +struct mm_struct;
hm, why is this needed?
> #define IS_UV() is_uv_system()
btw., why is there an ugly IS_UV() macro. All code should be using
is_uv_system() and IS_UV() should be removed.
Ingo
next prev parent reply other threads:[~2009-01-29 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 21:21 [PATCH] - UV fix compile error on IA64 & eliminate compiler warning Jack Steiner
2009-01-28 23:01 ` Harvey Harrison
2009-01-29 13:33 ` Ingo Molnar [this message]
2009-01-29 14:25 ` Jack Steiner
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=20090129133308.GE24391@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
/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