From: kernel test robot <lkp@intel.com>
To: Balbir Singh <balbirs@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
SeongJae Park <sj@kernel.org>
Subject: [akpm-mm:mm-unstable 187/225] arch/m68k/include/asm/page.h:20:27: error: lvalue required as unary '&' operand
Date: Tue, 16 Sep 2025 02:33:42 +0800 [thread overview]
Message-ID: <202509160214.gDtkbWC8-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: 0f409ed671a46de4b172899f7814a5bf37a33d86
commit: 00cd88c03fd1c3242be5726998b3bf47afbf17a1 [187/225] mm/rmap: extend rmap and migration support device-private entries
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20250916/202509160214.gDtkbWC8-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250916/202509160214.gDtkbWC8-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/202509160214.gDtkbWC8-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/build_bug.h:5,
from include/linux/init.h:5,
from mm/page_idle.c:2:
mm/page_idle.c: In function 'page_idle_clear_pte_refs_one':
>> arch/m68k/include/asm/page.h:20:27: error: lvalue required as unary '&' operand
20 | #define pmd_val(x) ((&x)->pmd)
| ^
include/linux/compiler.h:76:45: note: in definition of macro 'likely'
76 | # define likely(x) __builtin_expect(!!(x), 1)
| ^
arch/m68k/include/asm/motorola_pgtable.h:116:34: note: in expansion of macro 'pmd_val'
116 | #define pmd_present(pmd) (pmd_val(pmd) & _PAGE_TABLE)
| ^~~~~~~
mm/page_idle.c:74:36: note: in expansion of macro 'pmd_present'
74 | if (likely(pmd_present(pmdp_get(pvmw.pmd))))
| ^~~~~~~~~~~
vim +20 arch/m68k/include/asm/page.h
138ff3462f53a7 Greg Ungerer 2010-09-07 14
138ff3462f53a7 Greg Ungerer 2010-09-07 15 /*
138ff3462f53a7 Greg Ungerer 2010-09-07 16 * These are used to make use of C type-checking..
138ff3462f53a7 Greg Ungerer 2010-09-07 17 */
60e50f34b13e9e Mike Rapoport 2019-12-04 18 #if !defined(CONFIG_MMU) || CONFIG_PGTABLE_LEVELS == 3
ef22d8abd876e8 Peter Zijlstra 2020-01-31 19 typedef struct { unsigned long pmd; } pmd_t;
ef22d8abd876e8 Peter Zijlstra 2020-01-31 @20 #define pmd_val(x) ((&x)->pmd)
ef22d8abd876e8 Peter Zijlstra 2020-01-31 21 #define __pmd(x) ((pmd_t) { (x) } )
60e50f34b13e9e Mike Rapoport 2019-12-04 22 #endif
60e50f34b13e9e Mike Rapoport 2019-12-04 23
:::::: The code at line 20 was first introduced by commit
:::::: ef22d8abd876e805b604e8f655127de2beee2869 m68k: mm: Restructure Motorola MMU page-table layout
:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Geert Uytterhoeven <geert@linux-m68k.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-15 18:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202509160214.gDtkbWC8-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@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