From: <rongqing.li@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] QT4: use '-no-neon' if cpu does not support neon
Date: Fri, 1 Feb 2013 15:10:28 +0800 [thread overview]
Message-ID: <cover.1359688928.git.rongqing.li@windriver.com> (raw)
From: "Roy.Li" <rongqing.li@windriver.com>
*** BLURB HERE ***
The following changes since commit ab692ed618f83df2ce452769165314e70b867345:
gettext: Fix build with uclibc remove upstreamed patches (2013-01-27 13:52:49 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib qt4-check-neon-against-tune-features
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=qt4-check-neon-against-tune-features
Roy.Li (1):
QT4: use '-no-neon' if cpu does not support neon
meta/recipes-qt/qt4/qt4-embedded_4.8.4.bb | 4 ++--
meta/recipes-qt/qt4/qt4-x11-free_4.8.4.bb | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-02-01 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 7:10 rongqing.li [this message]
2013-02-01 7:10 ` [PATCH 1/1] QT4: use '-no-neon' if cpu does not support neon rongqing.li
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=cover.1359688928.git.rongqing.li@windriver.com \
--to=rongqing.li@windriver.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