From: Christian Brauner Date: Wed, 29 Oct 2025 14:50:48 +0000 (+0100) Subject: Merge patch series "filemap_* writeback interface cleanups v2" X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=211c43d0938dd57c2937366339f8b651e7990d1a;p=thirdparty%2Flinux.git Merge patch series "filemap_* writeback interface cleanups v2" Christoph Hellwig says: While looking at the filemap writeback code, I think adding filemap_fdatawrite_wbc ended up being a mistake, as all but the original btrfs caller should be using better high level interfaces instead. This series removes all these, switches btrfs to a more specific interfaces and also cleans up another too low-level interface. With this the writeback_control that is passed to the writeback code is only initialized in three places, although there are a lot more places in file system code that never reach the common writeback code. * patches from https://patch.msgid.link/20251024080431.324236-1-hch@lst.de: mm: rename filemap_fdatawrite_range_kick to filemap_flush_range mm: remove __filemap_fdatawrite_range mm: remove filemap_fdatawrite_wbc mm: remove __filemap_fdatawrite mm,btrfs: add a filemap_flush_nr helper btrfs: push struct writeback_control into start_delalloc_inodes btrfs: use the local tmp_inode variable in start_delalloc_inodes ocfs2: don't opencode filemap_fdatawrite_range in ocfs2_journal_submit_inode_data_buffers 9p: don't opencode filemap_fdatawrite_range in v9fs_mmap_vm_close mm: don't opencode filemap_fdatawrite_range in filemap_invalidate_inode Link: https://patch.msgid.link/20251024080431.324236-1-hch@lst.de Signed-off-by: Christian Brauner --- 211c43d0938dd57c2937366339f8b651e7990d1a