From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
<cip-dev@lists.cip-project.org>
Cc: <quirin.gylstorff@siemens.com>, <pluto.svc.chengdu.cn@siemens.com>
Subject: Re: [isar-cip-core][PATCH v2 0/2] Simplify integration of swupdate into downstream layers
Date: Fri, 14 Oct 2022 07:49:34 +0200 [thread overview]
Message-ID: <8d3cccb0-46c6-e1eb-9211-e427de153dec@siemens.com> (raw)
In-Reply-To: <20221013105938.332899-1-felix.moessbauer@siemens.com>
On 13.10.22 12:59, Felix Moessbauer wrote:
> Changes since v1:
>
> - moved initramfs-squashfs-hook from ebg-swu to swupdate kas file
> - minimal style fixes according to review comments
> - fixed typo in commit message
> - rebased onto current next
>
> This series simplifies the integration of the swupdate infrastructure into downstream layers and especially for debian stock kernels.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (2):
> fix: add squashfs hook to enforce load of module
> activate nodoc profile for swupdate build
>
> kas/opt/swupdate.yml | 1 +
> .../swupdate/swupdate_2021.11-1+debian-gbp.bb | 3 +++
> .../files/squashfs.hook | 25 +++++++++++++++++++
> .../initramfs-squashfs-hook_0.1.bb | 24 ++++++++++++++++++
> 4 files changed, 53 insertions(+)
> create mode 100644 recipes-initramfs/initramfs-squashfs-hook/files/squashfs.hook
> create mode 100644 recipes-initramfs/initramfs-squashfs-hook/initramfs-squashfs-hook_0.1.bb
>
Thanks, applied.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
parent reply other threads:[~2022-10-14 5:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221013105938.332899-1-felix.moessbauer@siemens.com>]
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=8d3cccb0-46c6-e1eb-9211-e427de153dec@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=felix.moessbauer@siemens.com \
--cc=pluto.svc.chengdu.cn@siemens.com \
--cc=quirin.gylstorff@siemens.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