From: Paul Bolle <pebolle@tiscali.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: NeilBrown <neilb@suse.de>, Jan Beulich <JBeulich@suse.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
mingo@elte.hu, tglx@linutronix.de,
james.t.kukunas@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/raid6: correctly check for assembler capabilities
Date: Tue, 16 Jun 2015 22:37:14 +0200 [thread overview]
Message-ID: <1434487034.2069.86.camel@x220> (raw)
In-Reply-To: <5580819F.1080802@zytor.com>
On Tue, 2015-06-16 at 13:05 -0700, H. Peter Anvin wrote:
> So this related to the CONFIG_AS_ symbols for assembly. We really would
> like to do things like actually adding dependencies on assembler or
> compiler support into Kconfig proper, rather than having two independent
> mechanisms. That way we could do, for example:
>
> config RAID6_AVX2
> depends on X86 && AS_AVX2
I have no idea what AS_AVX2 means, sorry. So what would it mean if
someone has a .config with
CONFIG_AS_AVX2=foo
Ie, what would happen if someone using a toolchain for which that would
not be possible tries to build a kernel with that symbol set? That
person's .config would end up containing
# CONFIG_AS_AVX2 is not set
or similar, right?
Paul Bolle
next prev parent reply other threads:[~2015-06-16 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 8:29 [PATCH] x86/raid6: correctly check for assembler capabilities Jan Beulich
2015-01-23 16:16 ` Thomas Gleixner
2015-01-28 5:02 ` NeilBrown
2015-02-03 20:31 ` Paul Bolle
2015-02-03 20:50 ` NeilBrown
2015-02-03 21:03 ` Paul Bolle
2015-02-03 21:09 ` NeilBrown
2015-02-03 21:24 ` Valentin Rothberg
2015-02-04 7:51 ` Jan Beulich
2015-06-16 19:46 ` H. Peter Anvin
2015-06-16 19:56 ` Paul Bolle
2015-06-16 20:05 ` H. Peter Anvin
2015-06-16 20:37 ` Paul Bolle [this message]
2015-06-16 20:42 ` H. Peter Anvin
2015-06-16 20:51 ` Paul Bolle
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=1434487034.2069.86.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=james.t.kukunas@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
--cc=tglx@linutronix.de \
--cc=valentinrothberg@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 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.