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: Tue, 13 Oct 2026 22:30:08 +0000 [thread overview]
Message-ID: <179193060814.1493834.7495972683379273028.git-patchwork-summary@kernel.org> (raw)
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Patch: [f2fs-dev] f2fs: fix termination of f2fs_sync_meta_caches()
Submitter: Seongjae Jeong <jsjlee1020@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1182851/
Lore link: https://lore.kernel.org/r/20261010074912.114840-1-jsjlee1020@gmail.com
Patch: [f2fs-dev,v1] f2fs: allow pinning empty compressed files
Submitter: Joanne Chang <joannechien@google.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1182273/
Lore link: https://lore.kernel.org/r/20261009095335.749891-1-joannechien@google.com
Series: [f2fs-dev,1/2] f2fs: fix to use bio_in_atomic() in f2fs_write_end_io()
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1182827/
Lore link: https://lore.kernel.org/r/20261010065546.1762091-1-chao@kernel.org
Patches: [f2fs-dev,1/2] f2fs: fix to use bio_in_atomic() in f2fs_write_end_io()
[f2fs-dev,2/2] f2fs: fix to use bio_in_atomic() in f2fs_read_end_io()
Series: [f2fs-dev,1/2] f2fs: cache: pin cached block in f2fs_end_cache_writeback()
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1177304/
Lore link: https://lore.kernel.org/r/20260930235435.3789910-1-chao@kernel.org
Patches: [f2fs-dev,1/2] f2fs: cache: pin cached block in f2fs_end_cache_writeback()
[f2fs-dev,2/2] f2fs: cache: pin cached block in f2fs_unlock_cache()
Patch: [f2fs-dev] f2fs: cache: count the temporary pins apart from the regular references
Submitter: Daeho Jeong <daeho43@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1179854/
Lore link: https://lore.kernel.org/r/20261005192114.1511660-1-daeho43@gmail.com
Patch: [f2fs-dev] f2fs: allow empty strings for journaled quota options
Submitter: Hengyu Liang <hengyul@cs.unc.edu>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1183078/
Lore link: https://lore.kernel.org/r/20261010165750.509939-1-hengyul@cs.unc.edu
Patch: [f2fs-dev] f2fs: fix to invalidate curseg if change_curseg() fails
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1184647/
Lore link: https://lore.kernel.org/r/20261013105538.3636822-1-chao@kernel.org
Patch: [f2fs-dev] Revert "f2fs: skip node_change lock for inline data writes"
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1180795/
Lore link: https://lore.kernel.org/r/20261007101738.2348038-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: convert inline quota files when turning quota on
Submitter: Daeho Jeong <daeho43@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1179192/
Lore link: https://lore.kernel.org/r/20261004170456.4104287-1-daeho43@gmail.com
Series: [f2fs-dev,1/5] f2fs: cache: introduce metadata_cache sysfs node
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1180846/
Lore link: https://lore.kernel.org/r/20261007114949.2428048-1-chao@kernel.org
Patches: [f2fs-dev,1/5] f2fs: cache: introduce metadata_cache sysfs node
[f2fs-dev,2/5] f2fs: cache: shrink meta and node caches in f2fs_balance_fs_bg
[f2fs-dev,4/5] f2fs: cache: support asynchronous write_end_io
[f2fs-dev,5/5] f2fs: introduce max_atc_write_bio_entry_cnt
Patch: [f2fs-dev] MAINTAINERS: f2fs: add dev branch to git tree entry
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1182831/
Lore link: https://lore.kernel.org/r/20261010065946.1763794-1-chao@kernel.org
Series: f2fs: support & optimize large folios for writable files
Submitter: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
Patchwork: https://patchwork.kernel.org/series/1182554/
Lore link: https://lore.kernel.org/r/20261009161224.4163796-1-zhaonanzhe@xiaomi.com
Patches: [f2fs-dev,v3,01/17] f2fs: extend folio state for large folio write path
[f2fs-dev,v3,07/17] f2fs: remove mappedtodisk flag usage in mmap write path
Patch: [f2fs-dev] f2fs: fix defragment writeback range truncation on 32-bit
Submitter: Zhan Xusheng <zhanxusheng1024@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1179751/
Lore link: https://lore.kernel.org/r/20261005154954.2097054-1-zhanxusheng@xiaomi.com
Patch: [f2fs-dev] f2fs: fix to check continuousness in f2fs_sync_meta_pages() correctly
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1177310/
Lore link: https://lore.kernel.org/r/20261001000616.3824366-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: check every cur_*_segno[] entry on readonly images
Submitter: Kaixuan Li <kaixuanli0131@gmail.com>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1168881/
Lore link: https://lore.kernel.org/r/20260918165507.1267942-1-kaixuanli0131@gmail.com
Patch: None
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1183727/
Lore link: https://lore.kernel.org/r/20261012091737.308136-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: fix to set sbi->log_blocksize in advance
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1177309/
Lore link: https://lore.kernel.org/r/20261001000450.3822520-1-chao@kernel.org
Patch: [f2fs-dev] f2fs: zone: fix to avoid bio split on sequential zone
Submitter: Chao Yu <chao@kernel.org>
Committer: Jaegeuk Kim <jaegeuk@kernel.org>
Patchwork: https://patchwork.kernel.org/series/1180796/
Lore link: https://lore.kernel.org/r/20261007101812.2348510-1-chao@kernel.org
Total patches: 24
--
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:[~2026-10-13 22:30 UTC|newest]
Thread overview: 183+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 22:30 patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-14 15:50 [f2fs-dev] Patchwork summary for: f2fs patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-30 17:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-22 15:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-14 15:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-08 20:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-09-03 16:10 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-27 4:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-25 15:40 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-21 15:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-13 16:01 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-12 20:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-11 4:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-08-05 21:20 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-07-28 1:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-07-14 3:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-06-24 8:59 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-06-22 20:00 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-06-17 14:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-06-16 2:50 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-06-15 15:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-22 4:30 patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-05-14 23:30 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-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=179193060814.1493834.7495972683379273028.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 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.