All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ke Liping <liping.ke@intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/4][Image Creator]Add mulitple extra cache fields request support
Date: Thu, 26 May 2011 10:53:38 +0800	[thread overview]
Message-ID: <cover.1306376361.git.liping.ke@intel.com> (raw)

From: Liping Ke <liping.ke@intel.com>

The series of patch are for mplementing multiple extra cache fields
request support.If user needs to request extra cache fields besides
CoreRecipeInfo fields, just add a new XXXRecipeInfo class definition
as Image Creator UI Hob Does.
For implementing this new feature, we refactory current cache code,
remove namedtuple and define corresponding class for dynamical cache
fields support per different cache usage request.

Liping Ke (4):
  Refactory Current Cache implementation
  Introduce extra cache class for image creator
  Introduce new param caches_array into Cache impl.
  Implement multiple extra cache fields request support

 bitbake/lib/bb/cache.py       |  532 ++++++++++++++++++++++-------------------
 bitbake/lib/bb/cache_extra.py |   54 ++++
 bitbake/lib/bb/cooker.py      |   70 ++++--
 bitbake/lib/bb/shell.py       |    2 +-
 bitbake/lib/bb/ui/hob.py      |    2 +
 5 files changed, 396 insertions(+), 264 deletions(-)
 create mode 100644 bitbake/lib/bb/cache_extra.py



WARNING: multiple messages have this Message-ID (diff)
From: Ke Liping <liping.ke@intel.com>
To: yocto@yoctoproject.org
Subject: [PATCH 0/4][Image Creator]Add mulitple extra cache fields request support
Date: Thu, 26 May 2011 10:51:59 +0800	[thread overview]
Message-ID: <cover.1306376361.git.liping.ke@intel.com> (raw)

From: Liping Ke <liping.ke@intel.com>

The series of patch are for mplementing multiple extra cache fields
request support.If user needs to request extra cache fields besides
CoreRecipeInfo fields, just add a new XXXRecipeInfo class definition
as Image Creator UI Hob Does.
For implementing this new feature, we refactory current cache code,
remove namedtuple and define corresponding class for dynamical cache
fields support per different cache usage request.

Liping Ke (4):
  Refactory Current Cache implementation
  Introduce extra cache class for image creator
  Introduce new param caches_array into Cache impl.
  Implement multiple extra cache fields request support

 bitbake/lib/bb/cache.py       |  532 ++++++++++++++++++++++-------------------
 bitbake/lib/bb/cache_extra.py |   54 ++++
 bitbake/lib/bb/cooker.py      |   70 ++++--
 bitbake/lib/bb/shell.py       |    2 +-
 bitbake/lib/bb/ui/hob.py      |    2 +
 5 files changed, 396 insertions(+), 264 deletions(-)
 create mode 100644 bitbake/lib/bb/cache_extra.py



             reply	other threads:[~2011-05-26  3:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  2:51 Ke Liping [this message]
2011-05-26  2:53 ` [PATCH 0/4][Image Creator]Add mulitple extra cache fields request support Ke Liping
2011-05-26  2:52 ` [PATCH 1/4][Image Creator]Refactory Current Cache implementation Ke Liping
2011-05-26  2:53   ` Ke Liping
2011-05-26  2:52 ` [PATCH 2/4][Image Creator]Introduce extra cache class for image creator Ke Liping
2011-05-26  2:53   ` Ke Liping
2011-05-26  2:52 ` [PATCH 3/4][Image Creator]Introduce new param caches_array into Cache impl Ke Liping
2011-05-26  2:53   ` Ke Liping
2011-05-26 10:27   ` Richard Purdie
2011-05-31  8:11     ` Ke, Liping
2011-05-26  2:52 ` [PATCH 4/4][Image Creator]Implement multiple extra cache fields request support Ke Liping
2011-05-26  2:53   ` Ke Liping
2011-05-26  3:11 ` [PATCH 0/4][Image Creator]Add mulitple " Ke, Liping
  -- strict thread matches above, loose matches on Subject: below --
2011-05-31  8:15 Ke Liping
2011-06-03  1:06 Ke Liping
2011-06-07 21:47 ` Richard Purdie

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=cover.1306376361.git.liping.ke@intel.com \
    --to=liping.ke@intel.com \
    --cc=poky@yoctoproject.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.