From: patchwork-bot+f2fs@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Mon, 18 Mar 2024 20:45:33 +0000 [thread overview]
Message-ID: <171079473309.25373.5641181802344355105.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: block: remove gfp_mask for blkdev_zone_mgmt()
Submitter: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Committer: Jens Axboe <axboe@kernel.dk>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=820775
Lore link: https://lore.kernel.org/r/20240128-zonefs_nofs-v3-0-ae3b7c8def61@wdc.com
Patches: [f2fs-dev,v3,1/5] zonefs: pass GFP_KERNEL to blkdev_zone_mgmt() call
[f2fs-dev,v3,2/5] dm: dm-zoned: guard blkdev_zone_mgmt with noio scope
[f2fs-dev,v3,3/5] btrfs: zoned: call blkdev_zone_mgmt in nofs scope
[f2fs-dev,v3,4/5] f2fs: guard blkdev_zone_mgmt with nofs scope
[f2fs-dev,v3,5/5] block: remove gfp_flags from blkdev_zone_mgmt
Series: Set casefold/fscrypt dentry operations through sb->s_d_op
Submitter: Gabriel Krisman Bertazi <krisman@suse.de>
Committer: Gabriel Krisman Bertazi <krisman@suse.de>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=828378
Lore link: https://lore.kernel.org/r/20240221171412.10710-1-krisman@suse.de
Patches: [f2fs-dev,v7,01/10] ovl: Always reject mounting over case-insensitive directories
[f2fs-dev,v7,02/10] fscrypt: Factor out a helper to configure the lookup dentry
[f2fs-dev,v7,03/10] fscrypt: Drop d_revalidate for valid dentries during lookup
[f2fs-dev,v7,04/10] fscrypt: Drop d_revalidate once the key is added
[f2fs-dev,v7,05/10] libfs: Merge encrypted_ci_dentry_ops and ci_dentry_ops
[f2fs-dev,v7,06/10] libfs: Add helper to choose dentry operations at mount-time
[f2fs-dev,v7,07/10] ext4: Configure dentry operations at dentry-creation time
[f2fs-dev,v7,08/10] f2fs: Configure dentry operations at dentry-creation time
[f2fs-dev,v7,09/10] ubifs: Configure dentry operations at dentry-creation time
[f2fs-dev,v7,10/10] libfs: Drop generic_set_encrypted_ci_d_ops
Patch: [f2fs-dev,GIT,PULL] f2fs update for 6.9-rc1
Submitter: Jaegeuk Kim <jaegeuk@kernel.org>
Committer: Linus Torvalds <torvalds@linux-foundation.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=836164
Lore link: https://lore.kernel.org/r/ZfiBt0gRe_Elp7hE@google.com
Total patches: 16
--
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:[~2024-03-18 20:45 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 20:45 patchwork-bot+f2fs [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-12 15:55 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs
2024-05-20 21:16 patchwork-bot+f2fs
2024-05-15 4:20 patchwork-bot+f2fs
2024-05-11 0:50 patchwork-bot+f2fs
2024-04-25 15:40 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-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-09-04 18:11 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=171079473309.25373.5641181802344355105.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 read-only IMAP folder(s) and NNTP newsgroup(s).