From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org
Subject: mm-next: manual merge of the akpm/mm-unstable branch
Date: Tue, 22 Sep 2026 21:17:56 +0200 [thread overview]
Message-ID: <0eff7de9-b379-472b-a1c3-07b55758b389@kernel.org> (raw)
Hi,
today's (well, and the last couple of days) mm-next merge of the
akpm/mm-unstable branch tree got a conflict in:
drivers/infiniband/hw/hfi1/file_ops.c
between the commit:
62f0f34fbd2b ("IB/hfi1: Fix the PIO_CRED credit-return mmap")
from Linus' tree and commit:
e7d9f14bb73b ("infiniband: update hfi1 to use remap_vmalloc_range()")
from the akpm/mm-unstable branch.
I resolved the conflicts manually:
diff --cc drivers/infiniband/hw/hfi1/file_ops.c
index 1a36f995c4f6,b02d1f1dbb27..680364fda856
--- a/drivers/infiniband/hw/hfi1/file_ops.c
+++ b/drivers/infiniband/hw/hfi1/file_ops.c
@@@ -325,8 -320,7 +320,8 @@@ static int hfi1_file_mmap(struct file *
memaddr = 0;
void *memvirt = NULL;
dma_addr_t memdma = 0;
- u8 subctxt, mapio = 0, vmf = 0, type;
+ u8 subctxt, mapio = 0, is_vmalloc = 0, type;
+ size_t memdmalen = 0;
ssize_t memlen = 0;
int ret = 0;
u16 ctxt;
@@@ -569,16 -546,13 +556,14 @@@
}
vm_flags_reset(vma, flags);
- mmap_cdbg(ctxt, subctxt, type, mapio, vmf, memaddr, memvirt, memdma,
+ mmap_cdbg(ctxt, subctxt, type, mapio, is_vmalloc, memaddr, memvirt, memdma,
memlen, vma);
- if (vmf) {
- vma->vm_pgoff = PFN_DOWN(memaddr);
- vma->vm_ops = &vm_ops;
- ret = 0;
+ if (is_vmalloc) {
+ ret = remap_vmalloc_range(vma, memvirt, 0);
} else if (memdma) {
ret = dma_mmap_coherent(&dd->pcidev->dev, vma,
- memvirt, memdma, memlen);
+ memvirt, memdma,
+ memdmalen ? memdmalen : memlen);
} else if (mapio) {
ret = io_remap_pfn_range(vma, vma->vm_start,
PFN_DOWN(memaddr),
--
Cheers,
David
next reply other threads:[~2026-09-22 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:17 David Hildenbrand (Arm) [this message]
2026-09-22 19:48 ` mm-next: manual merge of the akpm/mm-unstable branch Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2026-10-02 6:22 David Hildenbrand (Arm)
2026-10-02 8:15 ` Lorenzo Stoakes (ARM)
2026-10-02 12:16 ` David Hildenbrand (Arm)
2026-10-02 12:24 ` Lorenzo Stoakes (ARM)
2026-10-02 23:22 ` Andrew Morton
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=0eff7de9-b379-472b-a1c3-07b55758b389@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=mm-commits@vger.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 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.