From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL for v6.16] vfs writepages
Date: Fri, 23 May 2025 14:39:39 +0200 [thread overview]
Message-ID: <20250523-vfs-writepages-edcd7e528060@brauner> (raw)
Hey Linus,
/* Summary */
This converts vboxfs from ->writepage() to ->writepages(). This was the last
user of the ->writepage() method. So remove ->writepage() completely and all
references to it.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.16-rc1.writepage
for you to fetch changes up to fb5a381d624bf6ad3dc2541387feb5d835e1f377:
Merge patch series "Remove aops->writepage" (2025-04-07 09:36:50 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc1.writepage tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc1.writepage
----------------------------------------------------------------
Christian Brauner (1):
Merge patch series "Remove aops->writepage"
Matthew Wilcox (Oracle) (9):
9p: Add a migrate_folio method
vboxsf: Convert to writepages
migrate: Remove call to ->writepage
writeback: Remove writeback_use_writepage()
shmem: Add shmem_writeout()
i915: Use writeback_iter()
ttm: Call shmem_writeout() from ttm_backup_backup_page()
mm: Remove swap_writepage() and shmem_writepage()
fs: Remove aops->writepage
Documentation/admin-guide/cgroup-v2.rst | 2 +-
Documentation/filesystems/fscrypt.rst | 2 +-
Documentation/filesystems/locking.rst | 54 ++--------------------------
Documentation/filesystems/vfs.rst | 39 +++++---------------
block/blk-wbt.c | 2 +-
drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 32 +++++------------
drivers/gpu/drm/ttm/ttm_backup.c | 8 ++---
fs/9p/vfs_addr.c | 1 +
fs/buffer.c | 4 +--
fs/vboxsf/file.c | 47 ++++++++++++------------
include/linux/fs.h | 1 -
include/linux/shmem_fs.h | 7 ++--
mm/migrate.c | 60 ++++---------------------------
mm/page-writeback.c | 28 ++-------------
mm/page_io.c | 3 +-
mm/shmem.c | 33 ++++++++---------
mm/swap.h | 4 +--
mm/swap_state.c | 1 -
mm/swapfile.c | 2 +-
mm/vmscan.c | 29 ++++++++-------
20 files changed, 101 insertions(+), 258 deletions(-)
next reply other threads:[~2025-05-23 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:39 Christian Brauner [this message]
2025-05-26 18:35 ` pr-tracker-bot
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=20250523-vfs-writepages-edcd7e528060@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®