From: patchwork-bot+f2fs@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Mon, 04 Sep 2023 18:11:08 +0000 [thread overview]
Message-ID: <169385106853.19669.2971263993020474852.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: fs: implement multigrain timestamps
Submitter: Jeff Layton <jlayton@kernel.org>
Committer: Christian Brauner <brauner@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=773825
Lore link: https://lore.kernel.org/r/20230807-mgctime-v7-0-d1dec143a704@kernel.org
Patches: [f2fs-dev,v7,01/13] fs: remove silly warning from current_time
[f2fs-dev,v7,02/13] fs: pass the request_mask to generic_fillattr
[f2fs-dev,v7,03/13] fs: drop the timespec64 arg from generic_update_time
[f2fs-dev,v7,04/13] btrfs: have it use inode_update_timestamps
[f2fs-dev,v7,09/13] fs: add infrastructure for multigrain timestamps
[f2fs-dev,v7,10/13] tmpfs: add support for multigrain timestamps
[f2fs-dev,v7,12/13] ext4: switch to multigrain timestamps
[f2fs-dev,v7,13/13] btrfs: convert to multigrain timestamps
Series: [f2fs-dev,01/17] fs: unexport buffer_check_dirty_writeback
Submitter: Christoph Hellwig <hch@lst.de>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=742589
Lore link: https://lore.kernel.org/r/20230424054926.26927-2-hch@lst.de
Patches: [f2fs-dev,01/17] fs: unexport buffer_check_dirty_writeback
[f2fs-dev,04/17] fs: remove emergency_thaw_bdev
Series: fs: new accessors for inode->i_ctime
Submitter: Jeff Layton <jlayton@kernel.org>
Committer: Christian Brauner <brauner@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=762813
Lore link: https://lore.kernel.org/r/20230705185812.579118-1-jlayton@kernel.org
Patches: [f2fs-dev,v2,07/92] fs: add ctime accessors infrastructure
[f2fs-dev,v2,08/92] fs: new helper: simple_rename_timestamp
[f2fs-dev,v2,92/92] fs: rename i_ctime field to __i_ctime
Series: Simplify rejection of unexpected casefold inode flag
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Theodore Ts'o <tytso@mit.edu>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=776070
Lore link: https://lore.kernel.org/r/20230814182903.37267-1-ebiggers@kernel.org
Patches: [f2fs-dev,1/3] ext4: reject casefold inode flag without casefold feature
[f2fs-dev,2/3] ext4: remove redundant checks of s_encoding
[f2fs-dev,3/3] libfs: remove redundant checks of s_encoding
Series: [f2fs-dev,01/12] fs: export setup_bdev_super
Submitter: Christoph Hellwig <hch@lst.de>
Committer: Christian Brauner <brauner@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=772239
Lore link: https://lore.kernel.org/r/20230802154131.2221419-2-hch@lst.de
Patches: [f2fs-dev,01/12] fs: export setup_bdev_super
[f2fs-dev,02/12] nilfs2: use setup_bdev_super to de-duplicate the mount code
[f2fs-dev,05/12] ext4: make the IS_EXT2_SB/IS_EXT3_SB checks more robust
[f2fs-dev,07/12] fs: stop using get_super in fs_mark_dead
[f2fs-dev,08/12] fs: export fs_holder_ops
[f2fs-dev,09/12] ext4: drop s_umount over opening the log device
[f2fs-dev,10/12] ext4: use fs_holder_ops for the log device
Series: fsverity: simplify initcall and move sysctl registration
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Eric Biggers <ebiggers@google.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=762871
Lore link: https://lore.kernel.org/r/20230705212743.42180-1-ebiggers@kernel.org
Patches: [f2fs-dev,1/2] fsverity: simplify handling of errors during initcall
[f2fs-dev,2/2] fsverity: move sysctl registration out of signature.c
Patch: None
Submitter: Jeff Layton <jlayton@kernel.org>
Committer: Christian Brauner <brauner@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=762831
Lore link: https://lore.kernel.org/r/20230705190309.579783-41-jlayton@kernel.org
Patch: [f2fs-dev,GIT,PULL] f2fs update for 6.6
Submitter: Jaegeuk Kim <jaegeuk@kernel.org>
Committer: Linus Torvalds <torvalds@linux-foundation.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=781273
Lore link: https://lore.kernel.org/r/ZPJ7P1J+jbyL6Mve@google.com
Total patches: 27
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-09-04 18:11 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 18:11 patchwork-bot+f2fs [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-25 15:40 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs
2024-04-24 17:40 patchwork-bot+f2fs
2024-04-23 17:40 patchwork-bot+f2fs
2024-04-14 15:32 patchwork-bot+f2fs
2024-03-18 20:45 patchwork-bot+f2fs
2024-03-14 16:20 patchwork-bot+f2fs
2024-03-13 1:30 patchwork-bot+f2fs
2024-03-06 17:50 patchwork-bot+f2fs
2024-03-04 18:20 patchwork-bot+f2fs
2024-02-28 22:50 patchwork-bot+f2fs
2024-02-21 18:10 patchwork-bot+f2fs
2024-01-30 20:50 patchwork-bot+f2fs
2024-01-29 20:29 patchwork-bot+f2fs
2024-01-16 19:02 patchwork-bot+f2fs
2023-12-29 19:10 patchwork-bot+f2fs
2023-12-14 20:50 patchwork-bot+f2fs
2023-11-30 18:30 patchwork-bot+f2fs
2023-10-23 15:30 patchwork-bot+f2fs
2023-09-20 15:50 patchwork-bot+f2fs
2023-08-28 17:20 patchwork-bot+f2fs
2023-08-25 17:30 patchwork-bot+f2fs
2023-08-21 19:50 patchwork-bot+f2fs
2023-08-14 20:50 patchwork-bot+f2fs
2023-08-07 20:00 patchwork-bot+f2fs
2023-07-17 17:34 patchwork-bot+f2fs
2023-07-06 0:18 patchwork-bot+f2fs
2023-06-30 23:40 patchwork-bot+f2fs
2023-06-26 13:30 patchwork-bot+f2fs
2023-06-22 7:11 patchwork-bot+f2fs
2023-06-16 23:50 patchwork-bot+f2fs
2023-06-15 18:00 patchwork-bot+f2fs
2023-06-12 20:50 patchwork-bot+f2fs
2023-06-07 17:30 patchwork-bot+f2fs
2023-05-30 23:40 patchwork-bot+f2fs
2023-05-18 1:50 patchwork-bot+f2fs
2023-05-08 18:34 patchwork-bot+f2fs
2023-04-26 23:07 patchwork-bot+f2fs
2023-04-24 18:10 patchwork-bot+f2fs
2023-04-17 21:50 patchwork-bot+f2fs
2023-04-13 23:40 patchwork-bot+f2fs
2023-04-12 16:20 patchwork-bot+f2fs
2023-04-11 17:00 patchwork-bot+f2fs
2023-04-05 16:20 patchwork-bot+f2fs
2023-04-04 21:30 patchwork-bot+f2fs
2023-04-04 1:54 patchwork-bot+f2fs
2023-04-03 18:30 patchwork-bot+f2fs
2023-03-29 22:21 patchwork-bot+f2fs
2023-03-27 16:00 patchwork-bot+f2fs
2023-03-21 16:40 patchwork-bot+f2fs
2023-03-13 20:20 patchwork-bot+f2fs
2023-03-07 17:40 patchwork-bot+f2fs
2023-02-28 1:01 patchwork-bot+f2fs
2023-02-15 18:00 patchwork-bot+f2fs
2023-02-14 18:10 patchwork-bot+f2fs
2023-02-10 21:40 patchwork-bot+f2fs
2023-02-07 19:00 patchwork-bot+f2fs
2023-02-06 3:50 patchwork-bot+f2fs
2023-02-06 3:40 patchwork-bot+f2fs
2023-01-31 19:10 patchwork-bot+f2fs
2023-01-30 23:00 patchwork-bot+f2fs
2023-01-11 19:20 patchwork-bot+f2fs
2023-01-09 22:51 patchwork-bot+f2fs
2023-01-03 18:50 patchwork-bot+f2fs
2023-01-03 17:03 patchwork-bot+f2fs
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=169385106853.19669.2971263993020474852.git-patchwork-summary@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).