Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kang Kai <kai.kang@windriver.com>
Cc: bitbake-devel@lists.openembedded.org, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/3 V2] hob2: remove hard-coded image types map
Date: Fri, 07 Sep 2012 11:52:30 +0100	[thread overview]
Message-ID: <1347015150.7493.47.camel@ted> (raw)
In-Reply-To: <cover.1346121294.git.kai.kang@windriver.com>

On Tue, 2012-08-28 at 10:47 +0800, Kang Kai wrote:
> Hi Richard,
> 
> This is V2 for Yocto 2795.
> 
> Just add variable IMAGE_EXTENSION_live as you suggest, other image types are the same with the real image name extension names.
> 
> Add update the hob code accordingly.
> 
> Regards,
> Kai
> 
> The following changes since commit b4c5725af4cd85d5644f0373e2674e903c4eab2b:
> 
>   yocto-bsp: add missing xserver-xf86-config .bbappend for qemu (2012-08-25 14:47:07 +0100)
> 
> are available in the git repository at:
>   git://git.pokylinux.org/poky-contrib kangkai/hob2
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/hob2
> 
> Kang Kai (3):
>   hob2: remove the hard-coded images map
>   hob2: remove class hcc
>   image_types.bbclass: add variable for Hob

Merged to master, thanks.

Richard




      parent reply	other threads:[~2012-09-07 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28  2:47 [PATCH 0/3 V2] hob2: remove hard-coded image types map Kang Kai
2012-08-28  2:47 ` [PATCH 1/3] hob2: remove the hard-coded images map Kang Kai
2012-08-28  2:47 ` [PATCH 2/3] hob2: remove class hcc Kang Kai
2012-08-28  2:47 ` [PATCH 3/3] image_types.bbclass: add variable for Hob Kang Kai
2012-09-07  2:29 ` [PATCH 0/3 V2] hob2: remove hard-coded image types map Kang Kai
2012-09-07 10:52 ` Richard Purdie [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=1347015150.7493.47.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=kai.kang@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