linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Frank Sorenson <sorenson@redhat.com>, Jan Kara <jack@suse.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] fat: revise the FAT patches for mgtime series
Date: Thu, 10 Aug 2023 15:13:14 +0200	[thread overview]
Message-ID: <20230810-zieht-vorerst-e29e0ada149c@brauner> (raw)
In-Reply-To: <20230810-ctime-fat-v1-0-327598fd1de8@kernel.org>

On Thu, Aug 10, 2023 at 09:12:03AM -0400, Jeff Layton wrote:
> This is a respin of just the FAT patches for the multigrain ctime
> series. It's based on top of Christian's vfs.ctime branch, with this
> patch reverted:
> 
>     89b39bea91c4 fat: make fat_update_time get its own timestamp
> 
> Christian, let me know if you'd rather I resend the whole series.

Nono, that's fine as is. Thanks for taking care of all the fixups!

  parent reply	other threads:[~2023-08-10 13:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 13:12 [PATCH 0/2] fat: revise the FAT patches for mgtime series Jeff Layton
2023-08-10 13:12 ` [PATCH 1/2] fat: remove i_version handling from fat_update_time Jeff Layton
2023-08-10 13:21   ` Jan Kara
2023-08-10 17:31   ` OGAWA Hirofumi
2023-08-10 18:04   ` Frank Sorenson
2023-08-10 13:12 ` [PATCH 2/2] fat: make fat_update_time get its own timestamp Jeff Layton
2023-08-10 13:22   ` Jan Kara
2023-08-10 17:31   ` OGAWA Hirofumi
2023-08-10 18:05   ` Frank Sorenson
2023-08-10 13:13 ` Christian Brauner [this message]
2023-08-11  7:06 ` [PATCH 0/2] fat: revise the FAT patches for mgtime series Christian Brauner

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=20230810-zieht-vorerst-e29e0ada149c@brauner \
    --to=brauner@kernel.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jack@suse.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sorenson@redhat.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;
as well as URLs for NNTP newsgroup(s).