From: Christian Brauner <brauner@kernel.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
djwong@kernel.org, hch@infradead.org,
linux-fsdevel@vger.kernel.org, willy@infradead.org
Subject: Re: [PATCH v2 0/1] iomap: fix iomap_read_end() for already uptodate folios
Date: Wed, 19 Nov 2025 11:12:27 +0100 [thread overview]
Message-ID: <20251119-artgenossen-fleischfrei-aae8aa265bb6@brauner> (raw)
In-Reply-To: <20251118211111.1027272-1-joannelkoong@gmail.com>
On Tue, 18 Nov 2025 13:11:10 -0800, Joanne Koong wrote:
> This is a fix for commit f8eaf79406fe in the 'vfs-6.19.iomap' branch. It
> would be great if this could get folded up into that original commit, if it's
> not too late to do so.
>
> Thanks,
> Joanne
>
> [...]
Applied to the vfs-6.19.iomap branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.iomap branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.19.iomap
[1/1] iomap: fix iomap_read_end() for already uptodate folios
https://git.kernel.org/vfs/vfs/c/2e7278a6e951
prev parent reply other threads:[~2025-11-19 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 21:11 [PATCH v2 0/1] iomap: fix iomap_read_end() for already uptodate folios Joanne Koong
2025-11-18 21:11 ` [PATCH v2 1/1] " Joanne Koong
2025-11-19 10:12 ` Christian Brauner [this message]
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=20251119-artgenossen-fleischfrei-aae8aa265bb6@brauner \
--to=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=joannelkoong@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.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).