From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] make vm + live images can build together
Date: Wed, 2 Mar 2016 09:39:46 +0800 [thread overview]
Message-ID: <56D64462.7050102@windriver.com> (raw)
In-Reply-To: <CAJTo0LYUn-d-9S8U277QFAoYPp45yF3iRvffsFxTAT1RzB=C0Q@mail.gmail.com>
On 03/02/2016 12:36 AM, Burton, Ross wrote:
>
> On 29 February 2016 at 05:54, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
> syslinux.bbclass: make vm and live can be built together
> sanity.bbclass: remove conflict checking for image vm and live
>
>
> If I build a core-image-sato for intel-corei7-32 I get this warning:
>
> WARNING: core-image-sato-base-1.0-r0 do_bootimg: Found potential conflicted var
> INITRD, please use INITRD_LIVE rather than INITRD
I added this checking, we need fix from from meta-intel, I will send a patch to
meta-yocto yocto@yoctoproject.org to fix it.
// Robert
>
> Ross
prev parent reply other threads:[~2016-03-02 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 9:23 [PATCH 0/4] make vm + live images can build together Robert Yang
2016-02-24 9:23 ` [PATCH 1/4] image-live/boot-directdisk.bbclass: remove AUTO_SYSLINUXCFG Robert Yang
2016-02-24 9:23 ` [PATCH 2/4] boot-directdisk.bbclass: drop IS_VM chechking Robert Yang
2016-02-24 9:23 ` [PATCH 3/4] syslinux.bbclass: make vm and live can be built together Robert Yang
2016-02-24 9:23 ` [PATCH 4/4] sanity.bbclass: remove conflict checking for image vm and live Robert Yang
2016-02-29 5:54 ` [PATCH 0/4] make vm + live images can build together Robert Yang
2016-02-29 16:30 ` Burton, Ross
2016-03-01 16:36 ` Burton, Ross
2016-03-02 1:39 ` Robert Yang [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=56D64462.7050102@windriver.com \
--to=liezhi.yang@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 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.