From: Darrick J. Wong <djwong@kernel.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] fs/iomap: Fix buffered write page prefaulting
Date: Fri, 25 Mar 2022 17:03:37 -0700 [thread overview]
Message-ID: <20220326000337.GD8182@magnolia> (raw)
In-Reply-To: <20220325143701.144731-1-agruenba@redhat.com>
On Fri, Mar 25, 2022 at 03:37:01PM +0100, Andreas Gruenbacher wrote:
> Hello Linus,
>
> please consider pulling the following fix, which I've forgotten to send
> in the previous merge window. I've only improved the patch description
> since.
>
> Thank you very much,
> Andreas
>
> The following changes since commit 42eb8fdac2fc5d62392dcfcf0253753e821a97b0:
>
> Merge tag 'gfs2-v5.16-rc2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2021-11-17 15:55:07 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/write-page-prefaulting
>
> for you to fetch changes up to 631f871f071746789e9242e514ab0f49067fa97a:
>
> fs/iomap: Fix buffered write page prefaulting (2022-03-25 15:14:03 +0100)
When was this sent to fsdevel for public consideration? The last time I
saw any patches related to prefaulting in iomap was November.
--D
>
> ----------------------------------------------------------------
> Fix buffered write page prefaulting
>
> ----------------------------------------------------------------
> Andreas Gruenbacher (1):
> fs/iomap: Fix buffered write page prefaulting
>
> fs/iomap/buffered-io.c | 2 +-
> mm/filemap.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2022-03-26 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 14:37 [Cluster-devel] [GIT PULL] fs/iomap: Fix buffered write page prefaulting Andreas Gruenbacher
2022-03-26 0:03 ` Darrick J. Wong [this message]
2022-03-26 0:22 ` Andreas Gruenbacher
2022-03-26 1:41 ` Darrick J. Wong
2022-03-26 20:18 ` 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=20220326000337.GD8182@magnolia \
--to=djwong@kernel.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).