From: Phil Blundell <philb@gnu.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/8] tune-*: add PACKAGE_EXTRA_ARCHS entries starting with specific ARMPKGARCH
Date: Thu, 29 Nov 2012 23:25:10 +0000 [thread overview]
Message-ID: <1354231510.2452.5.camel@x121e.pbcl.net> (raw)
In-Reply-To: <e49fecdf22b26fddbd30a5bf23ef729a3e5f792e.1354230112.git.Martin.Jansa@gmail.com>
On Fri, 2012-11-30 at 00:12 +0100, Martin Jansa wrote:
> +PACKAGE_EXTRA_ARCHS_tune-arm920t = "${PACKAGE_EXTRA_ARCHS_tune-armv4t} arm920tt"
> +PACKAGE_EXTRA_ARCHS_tune-arm926ejs = "${PACKAGE_EXTRA_ARCHS_tune-armv5te} arm926ejste"
> +PACKAGE_EXTRA_ARCHS_tune-arm9tdmi = "${PACKAGE_EXTRA_ARCHS_tune-armv4t} arm9tdmit"
The last thing in each of those lines looks a bit weird. Not that I'm
saying that I think they're wrong, necessarily, but can you explain what
exactly they mean and why they are a sensible thing to have?
p.
next prev parent reply other threads:[~2012-11-29 23:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 23:12 [PATCH 0/8] Fixes for ARM tune files Martin Jansa
2012-11-29 23:12 ` [PATCH 1/8] tune-cortexa*, tune-xscale: fix ARMPKGARCH Martin Jansa
2012-11-29 23:12 ` [PATCH 2/8] tune-*: add PACKAGE_EXTRA_ARCHS entries starting with specific ARMPKGARCH Martin Jansa
2012-11-29 23:25 ` Phil Blundell [this message]
2012-11-29 23:12 ` [PATCH 3/8] arch-armv5: fix missing thumb TUNE_FEATURE in armv5t-vfp and following tunes Martin Jansa
2012-11-29 23:12 ` [PATCH 4/8] arch-armv[457]*: fix PACKAGE_EXTRA_ARCHS for bigendian TUNEs Martin Jansa
2012-11-29 23:12 ` [PATCH 5/8] arch-arm*: unify appending to TUNE_FEATURES Martin Jansa
2012-11-29 23:12 ` [PATCH 6/8] arch-armv4.inc: add --fix-v4bx to TARGET_LD_KERNEL_ARCH only for armv4 and strongarm1100 Martin Jansa
2012-11-29 23:12 ` [PATCH 7/8] arch-armv6: add tunes without vfp enabled Martin Jansa
2012-11-29 23:12 ` [PATCH 8/8] tune-cortexa*: add another TUNE which allows to enable cortexa* together with thumb and neon Martin Jansa
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=1354231510.2452.5.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox