From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/5] target: add symbols for i386/x86_64 cpu features
Date: Tue, 17 Jul 2012 09:33:12 +0200 [thread overview]
Message-ID: <20120717093312.5ea8e89e@skate> (raw)
In-Reply-To: <1342474650-10084-2-git-send-email-s.martin49@gmail.com>
Le Mon, 16 Jul 2012 23:37:26 +0200,
Samuel Martin <s.martin49@gmail.com> a ?crit :
> +# i386/x86_64 cpu features
> +config BR2_X86_CPU_HAS_MMX
> + depends on BR2_i386 || BR2_x86_64
> + bool
Is there any reason to have all those depends on BR2_i386 || BR2_x86_64
on those hidden options? Since they are hidden and only selected by
i386/x86_64 options, I don't think there's a point in keeping those
dependencies. If you agree, I can just fix that up when committing.
Best regards,
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-17 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:37 [Buildroot] [PATCH v5 0/5] OpenCV update and CPU fetures Samuel Martin
2012-07-16 21:37 ` [Buildroot] [PATCH v5 1/5] target: add symbols for i386/x86_64 cpu features Samuel Martin
2012-07-17 7:33 ` Thomas Petazzoni [this message]
2012-07-17 7:49 ` Samuel Martin
2012-07-17 9:17 ` Thomas Petazzoni
2012-07-17 9:43 ` Samuel Martin
2012-07-17 9:52 ` Thomas Petazzoni
2012-07-16 21:37 ` [Buildroot] [PATCH v5 2/5] libevas: refactor *_CONF_OPT assignment with cpu-feature options Samuel Martin
2012-07-16 21:37 ` [Buildroot] [PATCH v5 3/5] sdl_gfx: " Samuel Martin
2012-07-16 21:37 ` [Buildroot] [PATCH v5 4/5] sdl_sound: " Samuel Martin
2012-07-16 21:37 ` [Buildroot] [PATCH v5 5/5] opencv: bump to version 2.4.2 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=20120717093312.5ea8e89e@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 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.