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] vfs iomap
Date: Fri, 10 May 2024 13:45:49 +0200 [thread overview]
Message-ID: <20240510-vfs-iomap-eec693bccb02@brauner> (raw)
Hey Linus,
/* Summary */
This contains a few cleanups to the iomap code. Nothing particularly
stands out.
/* Testing */
clang: Debian clang version 16.0.6 (26)
gcc: (Debian 13.2.0-24)
All patches are based on v6.9-rc1 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
No known conflicts.
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.10.iomap
for you to fetch changes up to e1f453d4336d5d7fbbd1910532201b4a07a20a5c:
iomap: do some small logical cleanup in buffered write (2024-04-25 14:23:54 +0200)
Please consider pulling these changes from the signed vfs-6.10.iomap tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.10.iomap
----------------------------------------------------------------
Christoph Hellwig (1):
iomap: convert iomap_writepages to writeack_iter
Zhang Yi (5):
iomap: drop the write failure handles when unsharing and zeroing
iomap: don't increase i_size if it's not a write operation
iomap: use a new variable to handle the written bytes in iomap_write_iter()
iomap: make iomap_write_end() return a boolean
iomap: do some small logical cleanup in buffered write
fs/iomap/buffered-io.c | 119 +++++++++++++++++++++++++++----------------------
1 file changed, 65 insertions(+), 54 deletions(-)
next reply other threads:[~2024-05-10 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 11:45 Christian Brauner [this message]
2024-05-13 19:38 ` [GIT PULL] vfs iomap pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-03-22 10:14 Christian Brauner
2025-03-24 21:01 ` pr-tracker-bot
2024-03-08 10:12 Christian Brauner
2024-03-11 18:33 ` 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=20240510-vfs-iomap-eec693bccb02@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).