From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: [PATCH v2 0/3] Start to address umount problems
Date: Tue, 1 Oct 2024 17:13:56 +0200 [thread overview]
Message-ID: <cover.1727795639.git.jan.kiszka@siemens.com> (raw)
Changes in v2:
- break up the previously single patch into refactoring + fix
- add a fix for prematurely failing rootfs_do_unounts
Jan Kiszka (3):
image: Avoid breaking the build when mounts are no longer present on
umount
rootfs: Provide rootfs_do_umounts
initramfs: Add missing umounts after generation
meta/classes/image.bbclass | 21 ++-------------------
meta/classes/initramfs.bbclass | 2 ++
meta/classes/rootfs.bbclass | 32 ++++++++++++++++++++++++++++++++
3 files changed, 36 insertions(+), 19 deletions(-)
--
2.43.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/cover.1727795639.git.jan.kiszka%40siemens.com.
next reply other threads:[~2024-10-01 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 15:13 'Jan Kiszka' via isar-users [this message]
2024-10-01 15:13 ` [PATCH v2 1/3] image: Avoid breaking the build when mounts are no longer present on umount 'Jan Kiszka' via isar-users
2024-10-01 15:13 ` [PATCH v2 2/3] rootfs: Provide rootfs_do_umounts 'Jan Kiszka' via isar-users
2024-10-01 15:13 ` [PATCH v2 3/3] initramfs: Add missing umounts after generation 'Jan Kiszka' via isar-users
2024-10-01 22:33 ` [PATCH v2 0/3] Start to address umount problems 'Florian Bezdeka' via isar-users
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.1727795639.git.jan.kiszka@siemens.com \
--to=isar-users@googlegroups.com \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@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