From: Doug Chapman <doug.chapman@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
vtaras@openvz.org, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@suse.de>
Subject: RE: [PATCH] ia64: fix build failure on fs/quota.c
Date: Thu, 26 Jul 2007 17:58:45 -0400 [thread overview]
Message-ID: <1185487125.20910.30.camel@dchapman.boston.redhat.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A0205DE5E@scsmsx411.amr.corp.intel.com>
On Thu, 2007-07-26 at 14:24 -0700, Luck, Tony wrote:
> This issue wandered off onto a long thread "build fix for x86_64" which
> died out without a final patch. Here's the summary:
>
Ahh, thanks, I had not seen that thread.
> > +#if defined(CONFIG_X86_64) || (defined(CONFIG_IA64) && defined(CONFIG_COMPAT))
>
> It was pointed out that x86-64 also has a CONFIG_COMPAT, so the "right"
> #ifdef mess would be:
>
> #if defined(CONFIG_COMPAT) && (defined(CONFIG_IA64) || defined(CONFIG_X86_64))
>
> But this was thought too ugly. Andi Kleen proposed making a new CONFIG
> variable for this situation: CONFIG_COMPAT_FOR_U64_ALIGMNENT which could
> be set in ia64 and x86-64 Kconfig files with:
>
> config COMPAT_FOR_U64_ALIGMNENT
> def_bool COMPAT
>
> So the C-code would simply have:
>
> #if defined(COMPAT_COMPAT_FOR_U64_ALIGMNENT)
>
> (IIRC the syntax correctly). Peter Anvin had some worries about future
> issues ... but I think he agreed that this was Ok.
>
> Anyone still have any objections to this?
No objections here. I just tried this patch and it does fix my ia64
build issue. I agree it is a bit cleaner than the long #ifdef.
thanks,
- Doug
prev parent reply other threads:[~2007-07-26 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 17:15 Doug Chapman
2007-07-26 17:48 ` Doug Chapman
2007-07-26 21:24 ` Luck, Tony
2007-07-26 21:58 ` Doug Chapman [this message]
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=1185487125.20910.30.camel@dchapman.boston.redhat.com \
--to=doug.chapman@hp.com \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=vtaras@openvz.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®