From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/5] target: add symbols for i386/x86_64 cpu features
Date: Fri, 13 Jul 2012 23:26:22 +0200 [thread overview]
Message-ID: <20120713232622.5a42e405@skate> (raw)
In-Reply-To: <4FFBC796.9030204@mind.be>
Le Tue, 10 Jul 2012 08:11:34 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> I don't like these SSE4 configs which are not selected by anything. I understand
> that you need them for OpenCV, but it's not ideal.
>
> Maybe we need an extra subarchitecture config option to explicitly enable these?
Agreed, we should either have subarchitecture options that use those
SSE4 options, or we should not add those SSE4 options, and only add
them when those subarchitectures are added.
Samuel, can you take this into account and respin the patch set?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-13 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 22:42 [Buildroot] [PATCH v4 0/5] OpenCV update and CPU fetures Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 1/5] target: add symbols for i386/x86_64 cpu features Samuel Martin
2012-07-10 6:11 ` Arnout Vandecappelle
2012-07-13 21:26 ` Thomas Petazzoni [this message]
2012-07-13 21:57 ` Samuel Martin
2012-07-13 22:46 ` Thomas Petazzoni
2012-07-05 22:42 ` [Buildroot] [PATCH v4 2/5] libevas: refactor *_CONF_OPT assignment with cpu-feature options Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 3/5] sdl_gfx: " Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 4/5] sdl_sound: " Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 5/5] opencv: bump to version 2.4.1 Samuel Martin
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=20120713232622.5a42e405@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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