From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: zhe.he@windriver.com
Cc: bruce.ashfield@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 1/1] kernel: Add KERNEL_IMAGETYPES to build multi types of kernel at one time
Date: Fri, 07 Aug 2015 05:50:39 -0500 [thread overview]
Message-ID: <1438944639.30467.27.camel@linuxfoundation.org> (raw)
In-Reply-To: <64a413dc9fa38ee9d50b0837071775a3fe2fd48e.1438679154.git.zhe.he@windriver.com>
On Tue, 2015-08-04 at 17:17 +0800, zhe.he@windriver.com wrote:
> From: He Zhe <zhe.he@windriver.com>
>
> Add KERNEL_IMAGETYPES to support building packaging and installing
> multi types of kernel images, such as zImage uImage, at one time.
> KERNEL_IMAGETYPE works as it did.
>
> Fixes [YOCTO #6945].
>
> Signed-off-by: He Zhe <zhe.he@windriver.com>
> ---
> meta/classes/kernel-fitimage.bbclass | 21 +++---
> meta/classes/kernel-grub.bbclass | 46 ++++++++----
> meta/classes/kernel-uimage.bbclass | 22 +++---
> meta/classes/kernel.bbclass | 128 +++++++++++++++++++++++---------
> meta/conf/documentation.conf | 1 +
> meta/recipes-kernel/linux/linux-dtb.inc | 15 ++--
> 6 files changed, 159 insertions(+), 74 deletions(-)
I put this into master-next just to see what happened. I haven't
reviewed the code in more detail as yet. We saw:
https://autobuilder.yoctoproject.org/main/builders/build-appliance/builds/418/steps/BuildImages_1/logs/stdio
as one of the results and I suspect the linux-yocto packaging issue
comes from this. This suggests ipk packaging was not tested :(.
Cheers,
Richard
next prev parent reply other threads:[~2015-08-07 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 9:17 [PATCH v3 0/1] Yocto Bug #6945 zhe.he
2015-08-04 9:17 ` [PATCH v3 1/1] kernel: Add KERNEL_IMAGETYPES to build multi types of kernel at one time zhe.he
2015-08-07 10:50 ` Richard Purdie [this message]
2015-08-07 11:02 ` Richard Purdie
2015-08-05 9:09 ` [PATCH v3 0/1] Yocto Bug #6945 He Zhe
2015-08-05 18:33 ` Richard Purdie
2015-08-06 2:11 ` Bruce Ashfield
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=1438944639.30467.27.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=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