From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Huang Ying <ying.huang@intel.com>
Subject: Re: [linux-next:master 10352/10516] include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared
Date: Mon, 9 Sep 2024 20:45:55 -0700 [thread overview]
Message-ID: <20240909204555.ab57c729531c83a0685cfa8e@linux-foundation.org> (raw)
In-Reply-To: <202409100913.RxkfrKU6-lkp@intel.com>
On Tue, 10 Sep 2024 09:33:48 +0800 kernel test robot <lkp@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 100cc857359b5d731407d1038f7e76cd0e871d94
> commit: 5f445800cbdfc4b4185d496a43dfd78df63d2265 [10352/10516] Merge branch 'mm-everything' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20240910/202409100913.RxkfrKU6-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 14.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409100913.RxkfrKU6-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202409100913.RxkfrKU6-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> In file included from include/linux/ioport.h:15,
> from kernel/resource.c:15:
> kernel/resource.c: In function 'gfr_start':
> >> include/linux/mm.h:101:35: error: 'MAX_PHYSMEM_BITS' undeclared (first use in this function)
> 101 | # define PHYSMEM_END ((1ULL << MAX_PHYSMEM_BITS) - 1)
> | ^~~~~~~~~~~~~~~~
> include/linux/minmax.h:93:38: note: in definition of macro '__cmp_once_unique'
> 93 | ({ type ux = (x); type uy = (y); __cmp(op, ux, uy); })
> | ^
Thanks. "resource, kunit: add test case for region_intersects" is the culprit.
next prev parent reply other threads:[~2024-09-10 3:46 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 [this message]
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
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=20240909204555.ab57c729531c83a0685cfa8e@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=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