From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Fri, 11 Jul 2025 16:20:16 +0000 [thread overview]
Message-ID: <175225081679.2325425.7816502983073372451.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: f2fs folio conversions for 6.17
Submitter: Matthew Wilcox <willy@infradead.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=980132
Lore link: https://lore.kernel.org/r/20250708170359.111653-1-willy@infradead.org
Patches: [f2fs-dev,01/60] f2fs: Pass a folio to recover_dentry()
[f2fs-dev,02/60] f2fs: Pass a folio to recover_inode()
[f2fs-dev,03/60] f2fs: Pass a folio to recover_quota_data()
[f2fs-dev,04/60] f2fs: Pass a folio to f2fs_recover_inode_page()
[f2fs-dev,05/60] f2fs: Pass a folio to sanity_check_extent_cache()
[f2fs-dev,06/60] f2fs: Pass a folio to sanity_check_inode()
[f2fs-dev,07/60] f2fs: Pass a folio to f2fs_sanity_check_inline_data()
[f2fs-dev,08/60] f2fs: Pass a folio to inode_has_blocks()
[f2fs-dev,12/60] f2fs: Pass a folio to is_recoverable_dnode()
[f2fs-dev,13/60] f2fs: Pass a folio to set_dentry_mark()
[f2fs-dev,14/60] f2fs: Pass a folio to set_fsync_mark()
[f2fs-dev,15/60] f2fs: Pass a folio to set_mark()
[f2fs-dev,16/60] f2fs: Pass a folio to f2fs_allocate_data_block()
[f2fs-dev,17/60] f2fs: Pass a folio to f2fs_inode_chksum_set()
[f2fs-dev,18/60] f2fs: Pass a folio to f2fs_enable_inode_chksum()
[f2fs-dev,19/60] f2fs: Pass a folio to f2fs_inode_chksum()
[f2fs-dev,20/60] f2fs: Pass a folio to fill_node_footer_blkaddr()
[f2fs-dev,21/60] f2fs: Pass a folio to get_nid()
[f2fs-dev,22/60] f2fs: Pass a folio to set_cold_node()
[f2fs-dev,23/60] f2fs: Pass folios to copy_node_footer()
[f2fs-dev,24/60] f2fs: Pass a folio to fill_node_footer()
[f2fs-dev,25/60] f2fs: Pass a folio to cpver_of_node()
[f2fs-dev,26/60] f2fs: Pass a folio to f2fs_recover_xattr_data()
[f2fs-dev,27/60] f2fs: Pass a folio to is_fsync_dnode()
[f2fs-dev,28/60] f2fs: Pass a folio to is_dent_dnode()
[f2fs-dev,29/60] f2fs: Add fio->folio
[f2fs-dev,30/60] f2fs: Use folio_unlock() in f2fs_write_compressed_pages()
[f2fs-dev,31/60] f2fs: Pass a folio to is_cold_node()
[f2fs-dev,32/60] f2fs: Pass a folio to is_node()
[f2fs-dev,33/60] f2fs: Pass a folio to IS_DNODE()
[f2fs-dev,34/60] f2fs: Pass a folio to ofs_of_node()
[f2fs-dev,35/60] f2fs: Pass a folio to get_dnode_base()
[f2fs-dev,36/60] f2fs: Pass a folio to ADDRS_PER_PAGE()
[f2fs-dev,37/60] f2fs: Pass a folio to IS_INODE()
[f2fs-dev,38/60] f2fs: Add folio counterparts to page_private_flags functions
[f2fs-dev,40/60] f2fs: Convert set_page_private_data() to folio_set_f2fs_data()
[f2fs-dev,41/60] f2fs: Convert get_page_private_data() to folio_get_f2fs_data()
[f2fs-dev,42/60] f2fs: Pass a folio to f2fs_compress_write_end_io()
[f2fs-dev,43/60] f2fs: Use a folio in f2fs_merge_page_bio()
[f2fs-dev,44/60] f2fs: Use a bio in f2fs_submit_page_write()
[f2fs-dev,45/60] f2fs: Pass a folio to WB_DATA_TYPE() and f2fs_is_cp_guaranteed()
[f2fs-dev,46/60] f2fs: Use a folio iterator in f2fs_handle_step_decompress()
[f2fs-dev,47/60] f2fs: Pass a folio to f2fs_end_read_compressed_page()
[f2fs-dev,48/60] f2fs: Use a folio iterator in f2fs_verify_bio()
[f2fs-dev,49/60] f2fs: Pass a folio to f2fs_is_compressed_page()
[f2fs-dev,50/60] f2fs: Convert get_next_nat_page() to get_next_nat_folio()
[f2fs-dev,51/60] f2fs: Pass the nat_blk to __update_nat_bits()
[f2fs-dev,52/60] f2fs: Pass a folio to F2FS_NODE()
[f2fs-dev,53/60] f2fs: Pass a folio to f2fs_cache_compressed_page()
[f2fs-dev,54/60] f2fs: Use a folio in f2fs_encrypted_get_link()
[f2fs-dev,55/60] f2fs: Use F2FS_F_SB() in f2fs_read_end_io()
[f2fs-dev,56/60] f2fs: Remove clear_page_private_all()
[f2fs-dev,57/60] f2fs: Remove use of page from f2fs_write_single_data_page()
[f2fs-dev,58/60] f2fs: Pass a folio to f2fs_submit_merged_write_cond()
[f2fs-dev,59/60] f2fs: Pass a folio to __has_merged_page()
[f2fs-dev,60/60] f2fs: Remove F2FS_P_SB()
Patch: [f2fs-dev] f2fs: fix to avoid out-of-boundary access in devs.path
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=981365
Lore link: https://lore.kernel.org/r/20250711071450.207302-1-chao@kernel.org
Total patches: 57
--
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:[~2025-07-11 16:20 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-02 20:20 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-08-15 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-30 17:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-28 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-24 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-18 20:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-11 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-07-09 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-24 0:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-18 21:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-06-09 20:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-28 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-14 15:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-08 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-05-06 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-30 2:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-28 22:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-14 22:57 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-12 17:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-04-10 4:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-27 21:58 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-18 1:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-14 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-13 18:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-12 15:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 19:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-11 3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-05 14:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-04 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-03-01 1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-28 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-21 2:17 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12 3:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-12 2:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-10 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-02-06 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-29 0:56 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-25 1:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-22 21:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-21 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-17 21:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-13 18:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-01-08 18:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-12-16 16:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-23 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-21 16:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-18 17:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-11-07 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-28 17:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-14 20:11 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-10-10 20:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-25 3:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-09-16 21:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-30 20:51 patchwork-bot+f2fs--- via Linux-f2fs-devel
2024-08-05 23:30 patchwork-bot+f2fs
2024-07-24 2:16 patchwork-bot+f2fs
2024-07-15 14:40 patchwork-bot+f2fs
2024-07-03 15:20 patchwork-bot+f2fs
2024-06-24 17:40 patchwork-bot+f2fs
2024-06-12 15:55 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-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-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=175225081679.2325425.7816502983073372451.git-patchwork-summary@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=patchwork-bot+f2fs@kernel.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).