From: Borislav Petkov <bp@alien8.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Trevor Turner <turn3r.tr3v0r@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: K7/Athlon Optimization Causes Build Fail on Kernel 3.3 i686
Date: Wed, 28 Mar 2012 19:27:59 +0200 [thread overview]
Message-ID: <20120328172759.GC6765@x1.osrc.amd.com> (raw)
In-Reply-To: <4F7346BB.9020907@xenotime.net>
On Wed, Mar 28, 2012 at 10:13:31AM -0700, Randy Dunlap wrote:
> > in your config. K7 and EFI are from different epochs anyway and cannot
> > obviously be enabled both on the same system with the current Kconfig
> > for EFI.
> but the Kconfig files shouldn't allow such a failing .config to be
> created, or the Makefiles are inadequate, or <mumble something>....
Yeah, something like the following:
config MK7
bool "Athlon/Duron/K7"
depends on X86_32 && !EFI_STUB
or the other way around:
config EFI_STUB
bool "EFI stub support"
depends on EFI && !MK7
Hmm...
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-03-28 17:27 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 [this message]
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
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=20120328172759.GC6765@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=turn3r.tr3v0r@gmail.com \
/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