From: Vali Cobelea <valentin.cobelea@enea.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [B6019] [ppc64] Fixes a typo in tune config file for e6500
Date: Mon, 24 Mar 2014 17:06:11 +0200 [thread overview]
Message-ID: <533049E3.6040300@enea.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 61 bytes --]
Please review the attached patch.
Many thanks,
Valentin
[-- Attachment #2: 0001-ppc64-Fixes-a-typo-in-tune-config-file-for-e6500.patch --]
[-- Type: text/x-patch, Size: 1257 bytes --]
From 0a6844b003402164359c121706957c6f81e5fe79 Mon Sep 17 00:00:00 2001
From: Valentin Cobelea <valentin.cobelea@enea.com>
Date: Thu, 20 Mar 2014 15:36:43 +0100
Subject: [PATCH 1/1] [ppc64] Fixes a typo in tune config file for e6500.
This patch fixes a typo in the tune config file for ppc64 e6500
where the cpu type is a wrong one.
Signed-off-by: Valentin Cobelea <valentin.cobelea@enea.com>
---
meta/conf/machine/include/tune-ppce6500.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/tune-ppce6500.inc b/meta/conf/machine/include/tune-ppce6500.inc
index 1603bb4..ea743a3 100644
--- a/meta/conf/machine/include/tune-ppce6500.inc
+++ b/meta/conf/machine/include/tune-ppce6500.inc
@@ -18,4 +18,4 @@ PACKAGE_EXTRA_ARCHS_tune-ppc64e6500 = "${PACKAGE_EXTRA_ARCHS_tune-powerpc64} ppc
# glibc configure options to get e6500 specific library
GLIBC_EXTRA_OECONF_powerpc64 += "${@bb.utils.contains("TUNE_FEATURES", "e6500", "--with-cpu=e6500", "", d)}"
-GLIBC_EXTRA_OECONF_powerpc += "${@bb.utils.contains("TUNE_FEATURES", "e6500", "--with-cpu=603e", "", d)}"
+GLIBC_EXTRA_OECONF_powerpc += "${@bb.utils.contains("TUNE_FEATURES", "e6500", "--with-cpu=e6500", "", d)}"
--
1.7.10.4
reply other threads:[~2014-03-24 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=533049E3.6040300@enea.com \
--to=valentin.cobelea@enea.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