From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, ruansy.fnst@fujitsu.com,
jhubbard@nvidia.com, jgg@nvidia.com, djwong@kernel.org,
david@fromorbit.com, dan.j.williams@intel.com,
apopple@nvidia.com, akpm@linux-foundation.org,
akpm@linux-foundation.org
Subject: [folded-merged] fsdax-zero-the-edges-if-source-is-hole-or-unwritten-fix.patch removed from -mm tree
Date: Sun, 11 Dec 2022 17:17:03 -0800 [thread overview]
Message-ID: <20221212011704.58B88C433D2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fsdax-zero-the-edges-if-source-is-hole-or-unwritten-fix
has been removed from the -mm tree. Its filename was
fsdax-zero-the-edges-if-source-is-hole-or-unwritten-fix.patch
This patch was dropped because it was folded into fsdax-zero-the-edges-if-source-is-hole-or-unwritten.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: fsdax-zero-the-edges-if-source-is-hole-or-unwritten-fix
Date: Thu Dec 1 04:37:42 PM PST 2022
update dax_iomap_copy_around() kerneldoc, per Darrick
Cc: Alistair Popple <apopple@nvidia.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Darrick J. Wong <djwong@kernel.org>
Cc: Dave Chinner <david@fromorbit.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>
Cc: John Hubbard <jhubbard@nvidia.com>
Cc: Shiyang Ruan <ruansy.fnst@fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/dax.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--- a/fs/dax.c~fsdax-zero-the-edges-if-source-is-hole-or-unwritten-fix
+++ a/fs/dax.c
@@ -1092,7 +1092,8 @@ out:
}
/**
- * dax_iomap_copy_around - Copy the data from source to destination before write
+ * dax_iomap_copy_around - Prepare for an unaligned write to a shared/cow page
+ * by copying the data before and after the range to be written.
* @pos: address to do copy from.
* @length: size of copy operation.
* @align_size: aligned w.r.t align_size (either PMD_SIZE or PAGE_SIZE)
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
fsdax-zero-the-edges-if-source-is-hole-or-unwritten.patch
mm-disable-top-tier-fallback-to-reclaim-on-proactive-reclaim-fix.patch
reply other threads:[~2022-12-12 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221212011704.58B88C433D2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ruansy.fnst@fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.