From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v2 0/8] Implement ROOTFS postprocess commands
Date: Tue, 9 Apr 2019 14:29:07 +0200 [thread overview]
Message-ID: <20190409122915.14249-1-claudius.heine.ext@siemens.com> (raw)
From: Claudius Heine <ch@denx.de>
Hi,
this is version 2 of the ROOTFS postprocess patchset.
I merged the 'Clean image pipeline' into this one, since they were developed
and tested together.
Changes from v2:
- rebased on current next
- some more cleanup and refactoring patches added
- some changes to the postprocess patch, to better prepare for the
preprocessing patchset that will follow soon.
Claudius Heine (8):
image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed
image.bbclass: limit `du` to only one file system
meta/classes/targz-img: limit tarball creation to one file system
meta/classes/buildchroot: add check before each mounting and quotes
meta/image classes: refactor task stamps
meta/classes/*-img: remove 'inherit image' statements
meta/classes/image*: refactor image pipeline and image.bbclass
meta/classes/image: implement ROOTFS_POSTPROCESS_COMMAND
meta/classes/buildchroot.bbclass | 25 ++-
meta/classes/ext4-img.bbclass | 4 +-
meta/classes/fit-img.bbclass | 7 +-
meta/classes/image-cache-extension.bbclass | 26 +++
meta/classes/image-postproc-extension.bbclass | 46 ++++
meta/classes/image-sdk-extension.bbclass | 36 ++++
meta/classes/image-tools-extension.bbclass | 43 ++++
meta/classes/image.bbclass | 203 ++++--------------
meta/classes/rootfs.bbclass | 58 +++++
meta/classes/targz-img.bbclass | 6 +-
meta/classes/ubi-img.bbclass | 7 +-
meta/classes/ubifs-img.bbclass | 6 +-
meta/classes/wic-img.bbclass | 8 +-
13 files changed, 267 insertions(+), 208 deletions(-)
create mode 100644 meta/classes/image-cache-extension.bbclass
create mode 100644 meta/classes/image-postproc-extension.bbclass
create mode 100644 meta/classes/image-sdk-extension.bbclass
create mode 100644 meta/classes/image-tools-extension.bbclass
create mode 100644 meta/classes/rootfs.bbclass
--
2.20.1
next reply other threads:[~2019-04-09 12:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 12:29 claudius.heine.ext [this message]
2019-04-09 12:29 ` [PATCH v2 1/8] image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 2/8] image.bbclass: limit `du` to only one file system claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 3/8] meta/classes/targz-img: limit tarball creation to " claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 4/8] meta/classes/buildchroot: add check before each mounting and quotes claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 5/8] meta/image classes: refactor task stamps claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 6/8] meta/classes/*-img: remove 'inherit image' statements claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 7/8] meta/classes/image*: refactor image pipeline and image.bbclass claudius.heine.ext
2019-04-09 12:29 ` [PATCH v2 8/8] meta/classes/image: implement ROOTFS_POSTPROCESS_COMMAND claudius.heine.ext
2019-04-16 5:05 ` [PATCH v2 0/8] Implement ROOTFS postprocess commands 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=20190409122915.14249-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