linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Jeff Layton <jlayton@kernel.org>
Cc: jk@ozlabs.org, arnd@arndb.de, mpe@ellerman.id.au,
	npiggin@gmail.com, christophe.leroy@csgroup.eu,
	hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	borntraeger@linux.ibm.com, svens@linux.ibm.com,
	gregkh@linuxfoundation.org, arve@android.com, tkjos@android.com,
	maco@android.com, joel@joelfernandes.org, brauner@kernel.org,
	cmllamas@google.com, surenb@google.com,
	dennis.dalessandro@cornelisnetworks.com, jgg@ziepe.ca,
	leon@kernel.org, bwarrum@linux.ibm.com, rituagar@linux.ibm.com,
	ericvh@kernel.org, lucho@ionkov.net, asmadeus@codewreck.org,
	linux_oss@crudebyte.com, dsterba@suse.com, dhowells@redhat.com,
	marc.dionne@auristor.com, viro@zeniv.linux.org.uk,
	raven@themaw.net, luisbg@kernel.org, salah.triki@gmail.com,
	aivazian.tigran@gmail.com, ebiederm@xmission.com, kees
Subject: Re: [f2fs-dev] [PATCH v2 00/89] fs: new accessors for inode->i_ctime
Date: Mon, 04 Sep 2023 18:11:08 +0000	[thread overview]
Message-ID: <169385106881.19669.3510550425397118597.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230705185812.579118-1-jlayton@kernel.org>

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:

On Wed,  5 Jul 2023 14:58:09 -0400 you wrote:
> v2:
> - prepend patches to add missing ctime updates
> - add simple_rename_timestamp helper function
> - rename ctime accessor functions as inode_get_ctime/inode_set_ctime_*
> - drop individual inode_ctime_set_{sec,nsec} helpers
> 
> I've been working on a patchset to change how the inode->i_ctime is
> accessed in order to give us conditional, high-res timestamps for the
> ctime and mtime. struct timespec64 has unused bits in it that we can use
> to implement this. In order to do that however, we need to wrap all
> accesses of inode->i_ctime to ensure that bits used as flags are
> appropriately handled.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v2,07/92] fs: add ctime accessors infrastructure
    https://git.kernel.org/jaegeuk/f2fs/c/9b6304c1d537
  - [f2fs-dev,v2,08/92] fs: new helper: simple_rename_timestamp
    https://git.kernel.org/jaegeuk/f2fs/c/0c4767923ed6
  - [f2fs-dev,v2,92/92] fs: rename i_ctime field to __i_ctime
    https://git.kernel.org/jaegeuk/f2fs/c/13bc24457850

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-09-04 18:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230705185812.579118-1-jlayton@kernel.org>
     [not found] ` <20230705185812.579118-1-jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-05 18:58   ` [PATCH v2 07/92] fs: add ctime accessors infrastructure Jeff Layton
2023-07-05 18:58   ` [PATCH v2 08/92] fs: new helper: simple_rename_timestamp Jeff Layton
2023-07-05 18:58   ` [PATCH v2 92/92] fs: rename i_ctime field to __i_ctime Jeff Layton
2023-07-05 21:57   ` [PATCH v2 00/89] fs: new accessors for inode->i_ctime Jeff Layton
     [not found] ` <20230705185812.579118-2-jlayton@kernel.org>
     [not found]   ` <20230705185812.579118-2-jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-05 23:12     ` [PATCH v2 07/92] fs: add ctime accessors infrastructure Damien Le Moal
     [not found] ` <20230705185812.579118-4-jlayton@kernel.org>
     [not found]   ` <20230705185812.579118-4-jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-05 23:19     ` [PATCH v2 92/92] fs: rename i_ctime field to __i_ctime Damien Le Moal
2023-07-06 14:58   ` Jan Kara
     [not found] ` <a4e6cfec345487fc9ac8ab814a817c79a61b123a.camel@kernel.org>
     [not found]   ` <a4e6cfec345487fc9ac8ab814a817c79a61b123a.camel-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-06 15:16     ` [PATCH v2 00/89] fs: new accessors for inode->i_ctime Eric W. Biederman
2023-07-06 16:14       ` Jeff Layton
2023-07-07 12:42 ` Jeff Layton
2023-07-10 12:35   ` Christian Brauner
2023-07-10 13:32     ` Jeff Layton
2023-07-10 12:18 ` [PATCH v2 00/92] " Christian Brauner
     [not found] ` <20230705185812.579118-3-jlayton@kernel.org>
     [not found]   ` <3b403ef1-22e6-0220-6c9c-435e3444b4d3@kernel.org>
     [not found]     ` <3b403ef1-22e6-0220-6c9c-435e3444b4d3-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-06  0:04       ` [PATCH v2 08/92] fs: new helper: simple_rename_timestamp Jeff Layton
     [not found]     ` <7c783969641b67d6ffdfb10e509f382d083c5291.camel@kernel.org>
2023-07-06 21:02       ` [apparmor] " Seth Arnold
2023-07-07 10:50         ` Jeff Layton
     [not found]   ` <20230705185812.579118-3-jlayton-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-07-05 23:19     ` Damien Le Moal
2023-07-06 10:27     ` Jan Kara
2023-08-30  0:19   ` Al Viro
2023-08-30  0:48     ` Jeff Layton
2023-09-04 18:11 ` patchwork-bot+f2fs [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=169385106881.19669.3510550425397118597.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=aivazian.tigran@gmail.com \
    --cc=arnd@arndb.de \
    --cc=arve@android.com \
    --cc=asmadeus@codewreck.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=brauner@kernel.org \
    --cc=bwarrum@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=cmllamas@google.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=dhowells@redhat.com \
    --cc=dsterba@suse.com \
    --cc=ebiederm@xmission.com \
    --cc=ericvh@kernel.org \
    --cc=gor@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hca@linux.ibm.com \
    --cc=jgg@ziepe.ca \
    --cc=jk@ozlabs.org \
    --cc=jlayton@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=leon@kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=lucho@ionkov.net \
    --cc=luisbg@kernel.org \
    --cc=maco@android.com \
    --cc=marc.dionne@auristor.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=raven@themaw.net \
    --cc=rituagar@linux.ibm.com \
    --cc=salah.triki@gmail.com \
    --cc=surenb@google.com \
    --cc=svens@linux.ibm.com \
    --cc=tkjos@android.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).