From: patchwork-bot+f2fs@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Patchwork summary for: f2fs
Date: Tue, 28 Feb 2023 01:01:54 +0000 [thread overview]
Message-ID: <167754611479.27916.3941238065281013621.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: fsverity: support for non-4K pages
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Eric Biggers <ebiggers@google.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=706831
Lore link: https://lore.kernel.org/r/20221223203638.41293-1-ebiggers@kernel.org
Patches: [f2fs-dev,v2,01/11] fsverity: use unsigned long for level_start
[f2fs-dev,v2,02/11] fsverity: simplify Merkle tree readahead size calculation
[f2fs-dev,v2,03/11] fsverity: store log2(digest_size) precomputed
[f2fs-dev,v2,04/11] fsverity: use EFBIG for file too large to enable verity
[f2fs-dev,v2,05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block()
[f2fs-dev,v2,06/11] fsverity: support verification with tree block size < PAGE_SIZE
[f2fs-dev,v2,07/11] fsverity: support enabling with tree block size < PAGE_SIZE
[f2fs-dev,v2,08/11] ext4: simplify ext4_readpage_limit()
[f2fs-dev,v2,09/11] f2fs: simplify f2fs_readpage_limit()
[f2fs-dev,v2,10/11] fs/buffer.c: support fsverity in block_read_full_folio()
[f2fs-dev,v2,11/11] ext4: allow verity with fs block size < PAGE_SIZE
Series: Convert to filemap_get_folios_tag()
Submitter: Vishal Moola (Oracle) <vishal.moola@gmail.com>
Committer: Andrew Morton <akpm@linux-foundation.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=708912
Lore link: https://lore.kernel.org/r/20230104211448.4804-1-vishal.moola@gmail.com
Patches: [f2fs-dev,v5,01/23] pagemap: Add filemap_grab_folio()
[f2fs-dev,v5,02/23] filemap: Added filemap_get_folios_tag()
[f2fs-dev,v5,03/23] filemap: Convert __filemap_fdatawait_range() to use filemap_get_folios_tag()
[f2fs-dev,v5,04/23] page-writeback: Convert write_cache_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,05/23] afs: Convert afs_writepages_region() to use filemap_get_folios_tag()
[f2fs-dev,v5,06/23] btrfs: Convert btree_write_cache_pages() to use filemap_get_folio_tag()
[f2fs-dev,v5,07/23] btrfs: Convert extent_write_cache_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,08/23] ceph: Convert ceph_writepages_start() to use filemap_get_folios_tag()
[f2fs-dev,v5,09/23] cifs: Convert wdata_alloc_and_fillpages() to use filemap_get_folios_tag()
[f2fs-dev,v5,10/23] ext4: Convert mpage_prepare_extent_to_map() to use filemap_get_folios_tag()
[f2fs-dev,v5,11/23] f2fs: Convert f2fs_fsync_node_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,12/23] f2fs: Convert f2fs_flush_inline_data() to use filemap_get_folios_tag()
[f2fs-dev,v5,13/23] f2fs: Convert f2fs_sync_node_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,14/23] f2fs: Convert f2fs_write_cache_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,15/23] f2fs: Convert last_fsync_dnode() to use filemap_get_folios_tag()
[f2fs-dev,v5,16/23] f2fs: Convert f2fs_sync_meta_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,17/23] gfs2: Convert gfs2_write_cache_jdata() to use filemap_get_folios_tag()
[f2fs-dev,v5,18/23] nilfs2: Convert nilfs_lookup_dirty_data_buffers() to use filemap_get_folios_tag()
[f2fs-dev,v5,19/23] nilfs2: Convert nilfs_lookup_dirty_node_buffers() to use filemap_get_folios_tag()
[f2fs-dev,v5,20/23] nilfs2: Convert nilfs_btree_lookup_dirty_buffers() to use filemap_get_folios_tag()
[f2fs-dev,v5,21/23] nilfs2: Convert nilfs_copy_dirty_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,22/23] nilfs2: Convert nilfs_clear_dirty_pages() to use filemap_get_folios_tag()
[f2fs-dev,v5,23/23] filemap: Remove find_get_pages_range_tag()
Series: Add the test_dummy_encryption key on-demand
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Eric Biggers <ebiggers@google.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=719785
Lore link: https://lore.kernel.org/r/20230208062107.199831-1-ebiggers@kernel.org
Patches: [f2fs-dev,1/5] fscrypt: add the test dummy encryption key on-demand
[f2fs-dev,2/5] ext4: stop calling fscrypt_add_test_dummy_key()
[f2fs-dev,3/5] f2fs: stop calling fscrypt_add_test_dummy_key()
[f2fs-dev,4/5] fs/super.c: stop calling fscrypt_destroy_keyring() from __put_super()
[f2fs-dev,5/5] fscrypt: clean up fscrypt_add_test_dummy_key()
Patch: [f2fs-dev] MAINTAINERS: update fscrypt git repo
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Eric Biggers <ebiggers@google.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=712563
Lore link: https://lore.kernel.org/r/20230116233424.65657-1-ebiggers@kernel.org
Patch: [f2fs-dev,GIT,PULL] f2fs update for 6.3-rc1
Submitter: Jaegeuk Kim <jaegeuk@kernel.org>
Committer: Linus Torvalds <torvalds@linux-foundation.org>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=725347
Lore link: https://lore.kernel.org/r/Y/004is4VtYI7G2u@google.com
Patch: [f2fs-dev] MAINTAINERS: update fsverity git repo, list, and patchwork
Submitter: Eric Biggers <ebiggers@kernel.org>
Committer: Eric Biggers <ebiggers@google.com>
Patchwork: https://patchwork.kernel.org/project/f2fs/list/?series=712556
Lore link: https://lore.kernel.org/r/20230116232257.64377-1-ebiggers@kernel.org
Total patches: 42
--
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-02-28 1:02 UTC|newest]
Thread overview: 161+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 1:01 patchwork-bot+f2fs [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 23:30 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11 1:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-11 1:41 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-01 4:52 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-18 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-15 16:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-13 23:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-04-02 16:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-03-24 17:32 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-03-05 19:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-17 21:14 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-02-10 21:28 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-30 17:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-27 2:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-22 23:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-19 13:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-16 3:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-07 3:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16 19:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-16 0:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-09 17:18 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-03 21:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-12-02 18:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-24 18:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-11-11 22:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-16 18:24 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-10 16:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 18:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-06 17:38 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-10-02 20:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-29 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2025-09-02 20:20 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-11 16:20 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-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=167754611479.27916.3941238065281013621.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.