mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 04/12 for v6.18] iomap
Date: Fri, 26 Sep 2025 16:18:58 +0200	[thread overview]
Message-ID: <20250926-vfs-iomap-47b585a955ab@brauner> (raw)
In-Reply-To: <20250926-vfs-618-e880cf3b910f@brauner>

Hey Linus,

/* Summary */
This contains minor fixes and cleanups to the iomap code.
Nothing really stands out here.

/* Testing */

gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3+b1)

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 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.18-rc1.iomap

for you to fetch changes up to c59c965292f75e39cc4cfefb50d56d4b1900812e:

  Merge patch series "iomap: cleanups ahead of adding fuse support" (2025-09-19 14:17:16 +0200)

Please consider pulling these changes from the signed vfs-6.18-rc1.iomap tag.

Thanks!
Christian

----------------------------------------------------------------
vfs-6.18-rc1.iomap

----------------------------------------------------------------
Christian Brauner (1):
      Merge patch series "iomap: cleanups ahead of adding fuse support"

Darrick J. Wong (2):
      iomap: trace iomap_zero_iter zeroing activities
      iomap: error out on file IO when there is no inline_data buffer

 fs/iomap/buffered-io.c | 18 +++++++++++++-----
 fs/iomap/direct-io.c   |  3 +++
 fs/iomap/trace.h       |  1 +
 3 files changed, 17 insertions(+), 5 deletions(-)

  parent reply	other threads:[~2025-09-26 14:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 14:18 [GIT PULL 00/12 for v6.18] vfs 6.18 Christian Brauner
2025-09-26 14:18 ` [GIT PULL 01/12 for v6.18] misc Christian Brauner
2025-09-29  9:47   ` Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 02/12 for v6.18] mount Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 03/12 for v6.18] inode Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:18 ` Christian Brauner [this message]
2025-09-29 19:31   ` [GIT PULL 04/12 for v6.18] iomap pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 05/12 for v6.18] pidfs Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-10-01 14:18   ` Oleg Nesterov
2025-10-06 13:48     ` Christian Brauner
2025-10-07 14:34       ` Oleg Nesterov
2025-10-10 11:00         ` Christian Brauner
2025-09-26 14:19 ` [GIT PULL 06/12 for v6.18] rust Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 07/12 for v6.18] workqueue Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 08/12 for v6.18] core kernel Christian Brauner
2025-09-27 12:19   ` Sasha Levin
2025-09-29  9:53     ` Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 9/12 for v6.18] afs Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 10/12 for v6.18] namespaces Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 11/12 for v6.18] writeback Christian Brauner
2025-09-29 19:31   ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 12/12 for v6.18] async directory preliminaries Christian Brauner
2025-09-29 19:31   ` 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=20250926-vfs-iomap-47b585a955ab@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®