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 iomap
Date: Fri, 23 May 2025 14:49:22 +0200 [thread overview]
Message-ID: <20250523-vfs-iomap-e3468c51c620@brauner> (raw)
Hey Linus,
/* Summary */
This contains iomap updates for this cycle:
- More fallout and preparatory work associated with the folio batch prototype
posted a while back. Mainly this just cleans up some of the helpers
and pushes some pos/len trimming further down in the write begin path.
- Add missing flag descriptions to the iomap documentation.
/* 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.iomap
for you to fetch changes up to 2cb0e96cb01b4d165d0cee4d26996bb2b02a5109:
Merge patch series "iomap: misc buffered write path cleanups and prep" (2025-05-09 12:35:35 +0200)
Please consider pulling these changes from the signed vfs-6.16-rc1.iomap tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.16-rc1.iomap
----------------------------------------------------------------
Brian Foster (6):
iomap: resample iter->pos after iomap_write_begin() calls
iomap: drop unnecessary pos param from iomap_write_[begin|end]
iomap: drop pos param from __iomap_[get|put]_folio()
iomap: helper to trim pos/bytes to within folio
iomap: push non-large folio check into get folio path
iomap: rework iomap_write_begin() to return folio offset and length
Christian Brauner (2):
Merge patch series "Documentation: iomap: Add missing flags description"
Merge patch series "iomap: misc buffered write path cleanups and prep"
Ritesh Harjani (IBM) (2):
Documentation: iomap: Add missing flags description
iomap: trace: Add missing flags to [IOMAP_|IOMAP_F_]FLAGS_STRINGS
Documentation/filesystems/iomap/design.rst | 16 ++++-
fs/iomap/buffered-io.c | 100 +++++++++++++++++------------
fs/iomap/trace.h | 27 ++++++--
3 files changed, 93 insertions(+), 50 deletions(-)
next reply other threads:[~2025-05-23 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 12:49 Christian Brauner [this message]
2025-05-26 18:36 ` [GIT PULL for v6.16] vfs iomap 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-iomap-e3468c51c620@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;
as well as URLs for NNTP newsgroup(s).