From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>,
Matt Fleming <matt.fleming@intel.com>,
Trevor Turner <turn3r.tr3v0r@gmail.com>,
Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686
Date: Thu, 29 Mar 2012 11:28:40 -0700 [thread overview]
Message-ID: <4F74A9D8.1040808@zytor.com> (raw)
In-Reply-To: <20120329104822.GA17233@x1.osrc.amd.com>
On 03/29/2012 03:48 AM, Borislav Petkov wrote:
> On Thu, Mar 29, 2012 at 09:14:15AM +0100, Matt Fleming wrote:
>> Hmm... I think what might make more sense is to make EFI (not EFI_STUB)
>> depend on !MK7, since I doubt people actually need both MK7 and any EFI
>> firmware support.
>
> ... and EFI_STUB depends on EFI, yeah, true story.
>
> Here's an updated patch, Trevor pls try this one instead, thanks.
>
I like this one for urgent as a quick fix, but it doesn't solve the real
problem which is that boot/compressed shouldn't pick up these macros at all.
It should be possible to build with MK7 (which is an optimization
option) and EFI (a functionality option) since they don't inherently
conflict. It just doesn't necessarily have to happen *right now*.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-03-29 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 13:56 K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686 Trevor Turner
2012-03-27 17:29 ` Randy Dunlap
2012-03-28 0:03 ` Trevor Turner
2012-03-28 11:19 ` Borislav Petkov
2012-03-28 16:33 ` Trevor Turner
2012-03-28 17:10 ` Borislav Petkov
2012-03-28 17:13 ` Randy Dunlap
2012-03-28 17:27 ` Borislav Petkov
2012-03-29 7:48 ` Borislav Petkov
2012-03-29 8:14 ` Matt Fleming
2012-03-29 10:48 ` Borislav Petkov
2012-03-29 18:21 ` Trevor Turner
2012-03-29 18:28 ` H. Peter Anvin [this message]
2012-03-29 20:46 ` Borislav Petkov
2012-03-29 20:49 ` H. Peter Anvin
2012-03-30 7:47 ` Borislav Petkov
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=4F74A9D8.1040808@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=rdunlap@xenotime.net \
--cc=turn3r.tr3v0r@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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.