From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, bo.liu@linux.alibaba.com,
dan.j.williams@intel.com, dgilbert@redhat.com,
mm-commits@vger.kernel.org, mszeredi@redhat.com,
sebastien.boeuf@intel.com, stefanha@redhat.com,
vgoyal@redhat.com
Subject: [merged] fs-fuse-virtio_fsc-fix-for-mm-memremap_pages-convert-to-struct-range.patch removed from -mm tree
Date: Thu, 15 Oct 2020 16:16:11 -0700 [thread overview]
Message-ID: <20201015231611.jFaSm7UN7%akpm@linux-foundation.org> (raw)
The patch titled
Subject: fs/fuse/virtio_fs.c: fix for "mm/memremap_pages: convert to 'struct range'"
has been removed from the -mm tree. Its filename was
fs-fuse-virtio_fsc-fix-for-mm-memremap_pages-convert-to-struct-range.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: fs/fuse/virtio_fs.c: fix for "mm/memremap_pages: convert to 'struct range'"
Fix interaction with 22f3787e9d95e ("virtiofs: set up virtio_fs
dax_device").
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Sebastien Boeuf <sebastien.boeuf@intel.com>
Cc: Liu Bo <bo.liu@linux.alibaba.com>
Cc: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/fuse/virtio_fs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/fs/fuse/virtio_fs.c~fs-fuse-virtio_fsc-fix-for-mm-memremap_pages-convert-to-struct-range
+++ a/fs/fuse/virtio_fs.c
@@ -835,8 +835,7 @@ static int virtio_fs_setup_dax(struct vi
* initialize a struct resource from scratch (only the start
* and end fields will be used).
*/
- pgmap->res = (struct resource){
- .name = "virtio-fs dax window",
+ pgmap->range = (struct range){
.start = (phys_addr_t) cache_reg.addr,
.end = (phys_addr_t) cache_reg.addr + cache_reg.len - 1,
};
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm.patch
powerpc-mm-move-setting-pte-specific-flags-to-pfn_pte-fix.patch
xarray-add-xa_get_order-fix.patch
xarray-add-xas_split-fix.patch
mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix-2.patch
mm-memory_hotplug-simplify-page-offlining-fix.patch
checkpatch-warn-on-self-assignments-checkpatch-fixes.patch
checkpatch-emit-a-warning-on-embedded-filenames-fix.patch
fs-binfmt_elf-use-pt_load-p_align-values-for-suitable-start-address-fix.patch
linux-next-rejects.patch
mm-madvise-introduce-process_madvise-syscall-an-external-memory-hinting-api-fix-fix.patch
mm-madvise-introduce-process_madvise-syscall-an-external-memory-hinting-api-fix-fix-fix-fix-fix-fix-fix-fix.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2020-10-15 23:16 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=20201015231611.jFaSm7UN7%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bo.liu@linux.alibaba.com \
--cc=dan.j.williams@intel.com \
--cc=dgilbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=sebastien.boeuf@intel.com \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.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 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).