From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: He Zhe <zhe.he@windriver.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/2] Yocto Bug #6945
Date: Wed, 29 Jul 2015 09:23:25 -0400 [thread overview]
Message-ID: <55B8D3CD.2060200@windriver.com> (raw)
In-Reply-To: <55B8819B.6040407@windriver.com>
On 15-07-29 03:32 AM, He Zhe wrote:
> Ping.
>
> Is there any comments on this?
I'm obviously ok with the patch in its current RFC status. It works
and I've tested it in my tree (hence why I've been quiet on this
one).
If it meets the style for merging into core, and that it doesn't
break other layers we can't see .. I was hoping to hear from others.
Bruce
>
> Zhe
>
> On 07/28/2015 11:17 AM, He Zhe wrote:
>> Ping.
>>
>> On 07/27/2015 10:51 AM, He Zhe wrote:
>>> Ping.
>>>
>>> On 07/23/2015 03:48 PM, He Zhe wrote:
>>>> Ping.
>>>>
>>>> On 07/21/2015 03:23 PM, zhe.he@windriver.com wrote:
>>>>> From: He Zhe <zhe.he@windriver.com>
>>>>>
>>>>> - To support building packaging and installing multi types of kernel
>>>>> images, such as zImage uImage, at one time define KERNEL_IMAGETYPE
>>>>> as a list.
>>>>> - Modify wherever reference KERNEL_IMAGETYPE accordingly.
>>>>> - Pass mkimage in sysroot to kernel makefile by NATIVE_MKIMAGE to avoid
>>>>> depending on build machine's, when KEEPUIMAGE is "yes".
>>>>> - v2: update with the latest oe-core
>>>>>
>>>>> He Zhe (2):
>>>>> kernel: Define KERNEL_IMAGETYPE as a list
>>>>> kernel: Pass sysroot mkimage to kernel makefile
>>>>>
>>>>> meta/classes/image_types.bbclass | 6 +-
>>>>> meta/classes/kernel-fitimage.bbclass | 22 +++---
>>>>> meta/classes/kernel-grub.bbclass | 47 ++++++++----
>>>>> meta/classes/kernel-uimage.bbclass | 31 +++++---
>>>>> meta/classes/kernel.bbclass | 127 ++++++++++++++++++++++---------
>>>>> meta/conf/documentation.conf | 2 +-
>>>>> meta/lib/oeqa/controllers/masterimage.py | 2 +-
>>>>> meta/lib/oeqa/targetcontrol.py | 2 +-
>>>>> meta/recipes-kernel/linux/linux-dtb.inc | 15 ++--
>>>>> scripts/test-remote-image | 2 +-
>>>>> 10 files changed, 175 insertions(+), 81 deletions(-)
>>>>>
>
next prev parent reply other threads:[~2015-07-29 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 7:23 [PATCH v2 0/2] Yocto Bug #6945 zhe.he
2015-07-21 7:23 ` [PATCH v2 1/2] kernel: Define KERNEL_IMAGETYPE as a list zhe.he
2015-07-21 14:53 ` Christopher Larson
2015-07-22 2:29 ` He Zhe
2015-07-31 11:24 ` Richard Purdie
2015-07-31 11:45 ` He Zhe
2015-07-31 14:39 ` Richard Purdie
2015-07-21 7:23 ` [PATCH v2 2/2] kernel: Pass sysroot mkimage to kernel makefile zhe.he
2015-07-23 15:55 ` Richard Purdie
2015-07-24 10:16 ` He Zhe
2015-07-23 7:48 ` [PATCH v2 0/2] Yocto Bug #6945 He Zhe
2015-07-27 2:51 ` He Zhe
2015-07-28 3:17 ` He Zhe
2015-07-29 7:32 ` He Zhe
2015-07-29 13:23 ` Bruce Ashfield [this message]
2015-07-31 8:40 ` He Zhe
-- strict thread matches above, loose matches on Subject: below --
2016-02-19 9:56 zhe.he
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=55B8D3CD.2060200@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=zhe.he@windriver.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