From: Phil Blundell <pb@pbcl.net>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tune-i586-nlp: Add new tune file to support Quark/X1000 CPU
Date: Tue, 23 Jun 2015 18:19:51 +0100 [thread overview]
Message-ID: <1435079991.2483.418.camel@pbcl.net> (raw)
In-Reply-To: <D1AEE18F.D4FA6%dvhart@linux.intel.com>
On Tue, 2015-06-23 at 10:17 -0700, Darren Hart wrote:
> Hrm... The thing we need to avoid is quark machines accepting an i586
> package in lieu of a i586-nlp package. I don't think that's a problem here
> is it? The PACKAGE_EXTRA_ARCHS makes it so the i586-nlp package can be
> used on machines that require i586, but not vice versa - correct?
No, exactly the opposite to that.
p.
next prev parent reply other threads:[~2015-06-23 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 15:22 [PATCH] tune-i586-nlp: Add new tune file to support Quark/X1000 CPU Saul Wold
2015-06-23 16:02 ` Richard Purdie
2015-06-23 17:17 ` Darren Hart
2015-06-23 17:19 ` Phil Blundell [this message]
2015-06-24 15:10 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2015-06-29 14:10 Saul Wold
2015-07-01 16:03 ` Darren Hart
2015-07-02 15:53 ` Richard Purdie
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=1435079991.2483.418.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.