From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Richard Weinberger <richard@nod.at>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Berg <johannes.berg@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
Tiwei Bie <tiwei.btw@antgroup.com>
Subject: Re: linux-next: manual merge of the uml tree with the mm-stable tree
Date: Wed, 2 Apr 2025 10:20:16 +1100 [thread overview]
Message-ID: <20250402102016.6ab2367d@canb.auug.org.au> (raw)
In-Reply-To: <20250319105554.2e2f3aab@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
Hi all,
On Wed, 19 Mar 2025 10:55:54 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the uml tree got a conflict in:
>
> arch/um/kernel/mem.c
>
> between commits:
>
> 0d98484ee333 ("arch, mm: introduce arch_mm_preinit")
> 8afa901c147a ("arch, mm: make releasing of memory to page allocator more explicit")
>
> from the mm-stable tree and commit:
>
> e82cf3051e61 ("um: Update min_low_pfn to match changes in uml_reserved")
>
> from the uml tree.
>
> I fixed it up (I think - 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/um/kernel/mem.c
> index 379f33a1babf,61b5a5ede01c..000000000000
> --- a/arch/um/kernel/mem.c
> +++ b/arch/um/kernel/mem.c
> @@@ -66,11 -68,11 +68,12 @@@ void __init arch_mm_preinit(void
> map_memory(brk_end, __pa(brk_end), uml_reserved - brk_end, 1, 1, 0);
> memblock_free((void *)brk_end, uml_reserved - brk_end);
> uml_reserved = brk_end;
> + min_low_pfn = PFN_UP(__pa(uml_reserved));
> -
> - /* this will put all low memory onto the freelists */
> - memblock_free_all();
> max_pfn = max_low_pfn;
> +}
> +
> +void __init mem_init(void)
> +{
> kmalloc_ok = 1;
> }
>
This is nw a conflict between the uml tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-04-01 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 23:55 Stephen Rothwell
2025-04-01 23:20 ` Stephen Rothwell [this message]
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=20250402102016.6ab2367d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard@nod.at \
--cc=rppt@kernel.org \
--cc=tiwei.btw@antgroup.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 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®