linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: David Disseldorp <ddiss@suse.de>,
	linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [PATCH v4 0/4] initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME
Date: Wed, 10 Nov 2021 13:42:56 +0100	[thread overview]
Message-ID: <4ea6d5f982a389dd11da2e9db9972d946648e5fe.camel@suse.com> (raw)
In-Reply-To: <20211110123850.24956-1-ddiss@suse.de>

On Wed, 2021-11-10 at 13:38 +0100, David Disseldorp wrote:
> This patchset does some minor refactoring of cpio header magic
> checking
> and corrects documentation.
> Patch 4/4 allows cpio entry mtime preservation to be disabled via a
> new
> INITRAMFS_PRESERVE_MTIME Kconfig option.
> 
> Changes since v3, following feedback from Martin Wilck:
> - 4/4: keep vfs_utimes() call in do_copy() path
>   + drop [PATCH v3 4/5] initramfs: use do_utime() wrapper
> consistently
>   + add do_utime_path() helper
>   + clean up timespec64 initialisation
> - 4/4: move all mtime preservation logic to initramfs_mtime.h and
> drop
>   separate .c
> - 4/4: improve commit message
> 
>  .../early-userspace/buffer-format.rst         | 24 +++-----
>  init/Kconfig                                  | 10 ++++
>  init/initramfs.c                              | 57 +++--------------
> --
>  init/initramfs_mtime.h                        | 50 ++++++++++++++++
>  4 files changed, 75 insertions(+), 66 deletions(-)
> 

For the set:

Reviewed-by: Martin Wilck <mwilck@suse.com>



      parent reply	other threads:[~2021-11-10 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 12:38 [PATCH v4 0/4] initramfs: "crc" cpio format and INITRAMFS_PRESERVE_MTIME David Disseldorp
2021-11-10 12:38 ` [PATCH v4 1/4] initramfs: refactor do_header() cpio magic checks David Disseldorp
2021-11-10 12:38 ` [PATCH v4 2/4] initramfs: print helpful cpio error on "crc" magic David Disseldorp
2021-11-10 17:30   ` Matthew Wilcox
2021-11-10 20:54     ` David Disseldorp
2021-11-10 12:38 ` [PATCH v4 3/4] docs: remove mention of "crc" cpio format support David Disseldorp
2021-11-10 12:38 ` [PATCH v4 4/4] initramfs: add INITRAMFS_PRESERVE_MTIME Kconfig option David Disseldorp
2021-11-10 12:42 ` Martin Wilck [this message]

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=4ea6d5f982a389dd11da2e9db9972d946648e5fe.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=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).