From: He Zhe <zhe.he@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>,
Christopher Larson <clarson@kergoth.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/2] kernel: Define KERNEL_IMAGETYPE as a list
Date: Fri, 31 Jul 2015 19:45:31 +0800 [thread overview]
Message-ID: <55BB5FDB.4080707@windriver.com> (raw)
In-Reply-To: <1438341880.22462.25.camel@linuxfoundation.org>
On 07/31/2015 07:24 PM, Richard Purdie wrote:
> On Wed, 2015-07-22 at 10:29 +0800, He Zhe wrote:
>> On 07/21/2015 10:53 PM, Christopher Larson wrote:
>>> On Tue, Jul 21, 2015 at 12:23 AM, <zhe.he@windriver.com <mailto:zhe.he@windriver.com>>wrote:
>>>
>>> From: He Zhe <zhe.he@windriver.com <mailto: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.
>>>
>>> Fixes [YOCTO #6945].
>>>
>>> Signed-off-by: He Zhe <zhe.he@windriver.com <mailto:zhe.he@windriver.com>>
>>>
>>>
>>> Question, why not add KERNEL_IMAGETYPES, and make KERNEL_IMAGETYPE equal to your new KERNEL_IMAGETYPE_0?
>> Adding a new KERNEL_IMAGETYPES will also work. But it should be better
>> not to change the name of KERNEL_IMAGETYPE, so that those who have
>> used it don't have to change their code.
>>
>> Thank you for reviewing.
> I have to agree with Chris here, keeping KERNEL_IMAGETYPE as used today
> and equivalent to KERNEL_IMAGETYPE_0 and adding KERNEL_IMAGETYPES does
> seem like a cleaner way to implement this.
But it might mean we are going to check both KERNEL_IMAGETYPE and KERNEL_IMAGETYPES
to generate final image type list. Is that OK?
Thanks,
Zhe
> Cheers,
>
> Richard
>
>
>
>
>
next prev parent reply other threads:[~2015-07-31 11:45 UTC|newest]
Thread overview: 16+ 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 [this message]
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
2015-07-31 8:40 ` He Zhe
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=55BB5FDB.4080707@windriver.com \
--to=zhe.he@windriver.com \
--cc=bruce.ashfield@windriver.com \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.