linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, willy@infradead.org
Subject: [PATCH v3 0/5]: initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME
Date: Fri,  1 Oct 2021 15:42:51 +0200	[thread overview]
Message-ID: <20211001134256.5581-1-ddiss@suse.de> (raw)

This patchset does some minor refactoring of cpio header magic checking
and corrects documentation.
Patches 4/5 and 5/5 allow cpio entry mtime preservation to be disabled
via a new INITRAMFS_PRESERVE_MTIME Kconfig option.

Changes since previous version:
- curb enthusiasm in 1/5 commit message
- add cover letter

 .../early-userspace/buffer-format.rst         | 24 +++-----
 init/Kconfig                                  | 10 ++++
 init/Makefile                                 |  3 +
 init/initramfs.c                              | 57 +++----------------
 init/initramfs_mtime.c                        | 49 ++++++++++++++++
 init/initramfs_mtime.h                        | 11 ++++
 6 files changed, 88 insertions(+), 66 deletions(-)


             reply	other threads:[~2021-10-01 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 13:42 David Disseldorp [this message]
2021-10-01 13:42 ` [PATCH v3 1/5] initramfs: refactor do_header() cpio magic checks David Disseldorp
2021-10-01 13:42 ` [PATCH v3 2/5] initramfs: print helpful cpio error on "crc" magic David Disseldorp
2021-10-01 13:42 ` [PATCH v3 3/5] docs: remove mention of "crc" cpio format support David Disseldorp
2021-10-01 13:42 ` [PATCH v3 4/5] initramfs: use do_utime() wrapper consistently David Disseldorp
2021-10-01 13:42 ` [PATCH v3 5/5] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option David Disseldorp
2021-10-11 10:41 ` [PATCH v3 0/5]: initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
2021-11-05 12:03 ` David Disseldorp

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=20211001134256.5581-1-ddiss@suse.de \
    --to=ddiss@suse.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).