From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v2 0/4] Clean image pipeline
Date: Tue, 26 Mar 2019 08:23:08 +0100 [thread overview]
Message-ID: <20190326072312.10863-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Changes from v1:
- added patch to make kernel+initrd name fixed in DEPLOY_DIR
- fixed copy_boot_files task dependency
Claudius Heine (4):
image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed
meta/image classes: refactor task stamps
meta/classes/*-img: remove 'inherit image' statements
meta/classes/image*: refactor image pipeline and image.bbclass
meta/classes/ext4-img.bbclass | 4 +-
meta/classes/fit-img.bbclass | 7 +-
meta/classes/image-cache-extension.bbclass | 26 ++++
meta/classes/image-sdk-extension.bbclass | 36 ++++++
meta/classes/image-tools-extension.bbclass | 43 +++++++
meta/classes/image.bbclass | 135 +++++----------------
meta/classes/targz-img.bbclass | 4 +-
meta/classes/ubi-img.bbclass | 7 +-
meta/classes/ubifs-img.bbclass | 6 +-
meta/classes/wic-img.bbclass | 8 +-
10 files changed, 141 insertions(+), 135 deletions(-)
create mode 100644 meta/classes/image-cache-extension.bbclass
create mode 100644 meta/classes/image-sdk-extension.bbclass
create mode 100644 meta/classes/image-tools-extension.bbclass
--
2.20.1
next reply other threads:[~2019-03-26 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 7:23 claudius.heine.ext [this message]
2019-03-26 7:23 ` [PATCH v2 1/4] image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed claudius.heine.ext
2019-03-26 7:23 ` [PATCH v2 2/4] meta/image classes: refactor task stamps claudius.heine.ext
2019-03-26 7:23 ` [PATCH v2 3/4] meta/classes/*-img: remove 'inherit image' statements claudius.heine.ext
2019-03-26 7:23 ` [PATCH v2 4/4] meta/classes/image*: refactor image pipeline and image.bbclass claudius.heine.ext
2019-03-28 12:50 ` [PATCH v2 0/4] Clean image pipeline Maxim Yu. Osipov
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=20190326072312.10863-1-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.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