From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Catalin Marinas <catalin.marinas@arm•com>,
Will Deacon <will@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>
Cc: Ard Biesheuvel <ardb@kernel•org>,
Baolin Wang <baolin.wang@linux•alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the arm64 tree with the mm-stable tree
Date: Tue, 24 Oct 2023 09:52:34 +1100 [thread overview]
Message-ID: <20231024095234.1118e7dd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
Hi all,
Today's linux-next merge of the arm64 tree got a conflict in:
arch/arm64/include/asm/tlb.h
between commit:
55d2a0bd5ead ("mm: add statistics for PUD level pagetable")
from the mm-stable tree and commit:
3399ee709734 ("arm64: mm: Add support for folding PUDs at runtime")
from the arm64 tree.
Thanks, Catalin for the heads up, I just used your resolution.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/arm64/include/asm/tlb.h
index 846c563689a8,771077f34a6c..000000000000
--- a/arch/arm64/include/asm/tlb.h
+++ b/arch/arm64/include/asm/tlb.h
@@@ -96,10 -96,8 +96,12 @@@ static inline void __pmd_free_tlb(struc
static inline void __pud_free_tlb(struct mmu_gather *tlb, pud_t *pudp,
unsigned long addr)
{
- struct ptdesc *ptdesc = virt_to_ptdesc(pudp);
- if (pgtable_l4_enabled())
- tlb_remove_ptdesc(tlb, virt_to_ptdesc(pudp));
++ if (pgtable_l4_enabled()) {
++ struct ptdesc *ptdesc = virt_to_ptdesc(pudp);
+
- pagetable_pud_dtor(ptdesc);
- tlb_remove_ptdesc(tlb, ptdesc);
++ pagetable_pud_dtor(ptdesc);
++ tlb_remove_ptdesc(tlb, ptdesc);
++ }
}
#endif
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-10-23 22:52 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=20231024095234.1118e7dd@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ardb@kernel$(echo .)org \
--cc=baolin.wang@linux$(echo .)alibaba.com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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