From: Kang Kai <Kai.Kang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
Joe Slater <jslater@windriver.com>
Subject: Re: [PATCH 0/9] V2: Add machine qemuaarch64
Date: Thu, 18 Sep 2014 17:40:02 +0800 [thread overview]
Message-ID: <541AA872.8090201@windriver.com> (raw)
In-Reply-To: <CAJTo0LYPVqG9pPrTeMLyzjGH2=2mb7W6av4dYHJq5+ZZk+3r2A@mail.gmail.com>
On 2014年09月17日 23:11, Burton, Ross wrote:
> On 16 September 2014 16:06, Kai Kang <kai.kang@windriver.com> wrote:
>> V2:
>> * fix kernel linux-yocto build faiure
>> * redefine position of dynamic linker from /lib to /lib64
>> * other fixes of userspace packages
>>
>> Test with Joe Slater's patches:
>> * siteinfo: account for 32 and 64 bit arm
>> * sysprof: add aarch64 support
> So aarch64 support really needs qemuarm64 in oe-core to be tested, and
> qemuarm64 is a new feature, and we froze for new features two weeks
> ago. Blindly merging aarch64 patches that we can't currently test
> doesn't seem sensible.
>
> Could someone who is actually testing and working on the aarch64
> support (you?) manage a single branch that tracks master, so when 1.7
> branches off we can do a merge straight away.
OK. We will continue to work on arch aarch64 and do runtime tests.
--Kai
>
> Ross
>
>
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2014-09-18 9:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 15:06 [PATCH 0/9] V2: Add machine qemuaarch64 Kai Kang
2014-09-16 15:06 ` [PATCH 1/9] linux-yocto: depend on libgcc for aarch64 Kai Kang
2014-09-18 6:56 ` Khem Raj
2014-09-18 9:27 ` Kang Kai
2014-09-16 15:06 ` [PATCH 2/9] Add machine qemuarm64 Kai Kang
2014-09-16 15:06 ` [PATCH 3/9] gcc-4.9: redefine dynamic linker for aarch64 Kai Kang
2014-09-18 7:19 ` Khem Raj
2014-09-18 9:37 ` Kang Kai
2014-09-18 13:58 ` Mark Hatle
2014-09-18 14:13 ` Mark Hatle
2014-09-19 6:17 ` Kang Kai
2014-09-20 5:06 ` Mark Hatle
2014-09-16 15:06 ` [PATCH 4/9] libatomics-ops: add aarch64 target iniitial support Kai Kang
2014-09-16 15:06 ` [PATCH 5/9] qt4-native: add aarch64 support Kai Kang
2014-09-16 15:06 ` [PATCH 6/9] qt4: " Kai Kang
2014-09-16 15:06 ` [PATCH 7/9] qt4-embedded: disable webkit Kai Kang
2014-09-16 15:06 ` [PATCH 8/9] libpng: add neon option for aarch64 Kai Kang
2014-09-16 15:06 ` [PATCH 9/9] perf: disable libunwind support " Kai Kang
2014-09-18 7:07 ` Khem Raj
2014-09-18 9:38 ` Kang Kai
2014-09-17 9:13 ` [PATCH 0/9] V2: Add machine qemuaarch64 Kang Kai
2014-09-17 15:11 ` Burton, Ross
2014-09-18 9:40 ` Kang Kai [this message]
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=541AA872.8090201@windriver.com \
--to=kai.kang@windriver.com \
--cc=jslater@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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