All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Pasha Tatashin <pasha.tatashin@soleen.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Muchun Song <muchun.song@linux.dev>,
	Muchun Song <songmuchun@bytedance.com>
Subject: Re: linux-next: manual merge of the liveupdate tree with the mm tree
Date: Thu, 24 Sep 2026 20:36:43 +0300	[thread overview]
Message-ID: <arVfqzFi33jwJvel@kernel.org> (raw)
In-Reply-To: <arVZKNJKTwEqrFsF@sirena.org.uk>

On Thu, Sep 24, 2026 at 06:08:56PM +0100, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the liveupdate tree got a conflict in:
> 
>   mm/mm_init.c
> 
> between commit:
> 
>   a666a70d029d3 ("mm/mm_init: skip initializing shared vmemmap tail pages")
> 
> from the mm tree and commit:
> 
>   85d3615cea179 ("kho: rename KHO scratch to KHO bootmem")
> 
> from the liveupdate 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.

Looks correct to me.
Thanks!
 
> diff --combined mm/mm_init.c
> index dc835f753ea9a,24a53d5f0893d..0000000000000
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@@ -29,7 -29,6 +29,7 @@@
>   #include <linux/cma.h>
>   #include <linux/crash_dump.h>
>   #include <linux/execmem.h>
>  +#include <linux/sizes.h>
>   #include <linux/vmstat.h>
>   #include <linux/kexec_handover.h>
>   #include <linux/hugetlb.h>
> @@@ -678,33 -677,21 +678,33 @@@ static inline void fixup_hashdist(void
>   static inline void fixup_hashdist(void) {}
>   #endif /* CONFIG_NUMA */
>   
>  -#if defined(CONFIG_ZONE_DEVICE) || defined(CONFIG_DEFERRED_STRUCT_PAGE_INIT)
>   static __meminit void pageblock_migratetype_init_range(unsigned long pfn,
>  -		unsigned long nr_pages, int migratetype, bool atomic)
>  +		unsigned long nr_pages, int migratetype, bool isolate, bool atomic)
>   {
>   	const unsigned long end = pfn + nr_pages;
>   
>   	for (pfn = pageblock_align(pfn); pfn < end; pfn += pageblock_nr_pages) {
> - 		enum migratetype mt = kho_scratch_migratetype(pfn, migratetype);
> + 		enum migratetype mt = kho_bootmem_migratetype(pfn, migratetype);

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2026-09-24 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 17:08 linux-next: manual merge of the liveupdate tree with the mm tree Mark Brown
2026-09-24 17:36 ` Mike Rapoport [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-09-24 18:53 Mark Brown

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=arVfqzFi33jwJvel@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=songmuchun@bytedance.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 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.