From: Andrew Morton <akpm@linux-foundation.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [linux-next:master 10352/10516] include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared
Date: Tue, 10 Sep 2024 20:45:34 -0700 [thread overview]
Message-ID: <20240910204534.94fe988e2865c0e187b7653b@linux-foundation.org> (raw)
In-Reply-To: <87ttenvw0i.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Wed, 11 Sep 2024 09:06:53 +0800 "Huang, Ying" <ying.huang@intel.com> wrote:
> > linux-next?) requires the presence of ea72ce5da228 ("x86/kaslr: Expose
> > and use the end of the physical memory address space"), which is not
> > present in mm.git. Yet mm.git exhibits the build failure.
>
> The original test report is against linux-next tree instead mm tree.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> The first bad commit (bisection result) is:
>
> 5f445800cbdfc4b4185d496a43dfd78df63d2265 [10352/10516] Merge branch 'mm-everything' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> That is, mm tree is merged in linux-next, and commit ea72ce5da228
> ("x86/kaslr: Expose and use the end of the physical memory address
> space") is merged in linux-next too. In fact, there's a merge conflict
> for MAX_PHYSMEM_BITS related code. Maybe this can be part of merge
> conflict resolving patch?
>
> Hi, Stephen,
>
> Can you use the patch above as part of merged conflict resolving patch
> for patch
>
> e2941fe697c8 ("resource, kunit: add test case for region_intersects()")
>
> You have resolved it in
>
> https://lore.kernel.org/lkml/20240909100043.60668995@canb.auug.org.au/
mm-unstable is presently broken, and fixing up linux-next won't change that.
I'd prefer to fix mm-stable and then provide Linus directions for merging that
with the x86 tree.
next prev parent reply other threads:[~2024-09-11 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 1:33 kernel test robot
2024-09-10 3:45 ` Andrew Morton
2024-09-10 5:42 ` Huang, Ying
2024-09-10 17:40 ` Andrew Morton
2024-09-11 1:06 ` Huang, Ying
2024-09-11 2:32 ` Stephen Rothwell
2024-09-11 3:45 ` Andrew Morton [this message]
2024-09-11 5:18 ` Huang, Ying
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=20240910204534.94fe988e2865c0e187b7653b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.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