mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul@pwsan.com>,
	David Hildenbrand <david@kernel.org>,
	Jisheng Zhang <jszhang@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Muchun Song <muchun.song@linux.dev>,
	Paul Walmsley <pjw@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>
Subject: Re: linux-next: manual merge of the risc-v tree with the mm tree
Date: Mon, 12 Oct 2026 19:01:37 -0700	[thread overview]
Message-ID: <20261012190137.9734b57074f35e540733b9e3@linux-foundation.org> (raw)
In-Reply-To: <as0D2sHzh_UnNF5L@sirena.org.uk>

On Mon, 12 Oct 2026 16:59:22 +0100 Mark Brown <broonie@kernel.org> wrote:

> Hi all,
> 
> Today's linux-next merge of the risc-v tree got a conflict in:
> 
>   arch/riscv/mm/init.c
> 
> between commit:
> 
>   f02f1d1437449 ("riscv/mm: fix hotplug page-table destructor handling")
> 
> from the mm tree and commit:
> 
>   79113093e9dc3 ("riscv: convert pgtable_l4|l5_enabled to inline function")
> 
> from the risc-v 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.

Thanks.

> diff --combined arch/riscv/mm/init.c
> index 6f6b04795bb23,e2b738ca90cf3..0000000000000
> --- a/arch/riscv/mm/init.c
> +++ b/arch/riscv/mm/init.c

Well that's ugly.

I'll disable "riscv/mm: fix hotplug page-table destructor handling" for
now to make this go away.

A decent approach would be to add that patch via the riscv tree.  Muchun,
please confirm that this has no dependencies on anything else?

Otherwise I'll leave it disabled and revisit after -rc1.



  reply	other threads:[~2026-10-13  2:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 15:59 Mark Brown
2026-10-13  2:01 ` Andrew Morton [this message]
2026-10-13  2:29   ` Muchun Song
  -- strict thread matches above, loose matches on Subject: below --
2025-04-03 23:54 Stephen Rothwell
2025-04-06 23:35 ` Stephen Rothwell

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=20261012190137.9734b57074f35e540733b9e3@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=david@kernel.org \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=paul@pwsan.com \
    --cc=pjw@kernel.org \
    --cc=rppt@kernel.org \
    --cc=vbabka@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

all inboxes | Powered by JetHome®