public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Paul Walmsley <pjw@kernel.org>
Subject: linux-next: manual merge of the mm-stable tree with the mm-hotfixes tree
Date: Thu, 25 Sep 2025 13:59:06 +0100	[thread overview]
Message-ID: <aNU8moQVmqvduSPU@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]

Hi all,

Today's linux-next merge of the mm-stable tree got a conflict in:

  arch/riscv/include/asm/pgtable.h

between commit:

  668208b161a0b ("riscv: use an atomic xchg in pudp_huge_get_and_clear()")

from the mm-hotfixes tree and commit:

  546e42c8c6d94 ("riscv: Use an atomic xchg in pudp_huge_get_and_clear()")

from the mm-stable tree.

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.

diff --cc arch/riscv/include/asm/pgtable.h
index 8150677429398,e69346307e786..0000000000000
--- a/arch/riscv/include/asm/pgtable.h
+++ b/arch/riscv/include/asm/pgtable.h
@@@ -944,15 -944,9 +944,15 @@@ static inline int pudp_test_and_clear_y
  
  #define __HAVE_ARCH_PUDP_HUGE_GET_AND_CLEAR
  static inline pud_t pudp_huge_get_and_clear(struct mm_struct *mm,
- 					    unsigned long address,  pud_t *pudp)
+ 					    unsigned long address, pud_t *pudp)
  {
 +#ifdef CONFIG_SMP
- 	pud_t pud = __pud(xchg(&pudp->pud, 0));
+ 	pud_t pud = __pud(atomic_long_xchg((atomic_long_t *)pudp, 0));
 +#else
 +	pud_t pud = *pudp;
 +
 +	pud_clear(pudp);
 +#endif
  
  	page_table_check_pud_clear(mm, pud);
  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-09-25 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 12:59 Mark Brown [this message]
2025-09-25 18:26 ` linux-next: manual merge of the mm-stable tree with the mm-hotfixes tree 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=aNU8moQVmqvduSPU@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexghiti@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pjw@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