From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: [jic23-cxl-staging:arm-numa-fixes 6/11] arch/arm64/include/asm/sparsemem.h:34:29: error: redefinition of 'phys_to_target_node'
Date: Thu, 16 May 2024 01:16:10 +0800 [thread overview]
Message-ID: <202405160145.lGsTS81g-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/cxl-staging.git arm-numa-fixes
head: d077bf9570e8024f6d670d5662b62778715084fc
commit: 67c8bdd7ebb95e48944e4ebffe0a6ce6b68d1663 [6/11] arm64: memblock: Introduce a generic phys_addr_to_target_node()
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20240516/202405160145.lGsTS81g-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240516/202405160145.lGsTS81g-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/202405160145.lGsTS81g-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/linux/page-flags-layout.h:30,
from include/linux/mmzone.h:20,
from include/linux/swap.h:7,
from arch/arm64/mm/init.c:12:
arch/arm64/include/asm/sparsemem.h:32:36: error: redefinition of 'memory_add_physaddr_to_nid'
32 | #define memory_add_physaddr_to_nid memory_add_physaddr_to_nid
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm64/mm/init.c:63:5: note: in expansion of macro 'memory_add_physaddr_to_nid'
63 | int memory_add_physaddr_to_nid(u64 start)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/linux/cpumask.h:17,
from arch/arm64/include/asm/cpufeature.h:27,
from arch/arm64/include/asm/ptrace.h:11,
from arch/arm64/include/asm/irqflags.h:10,
from include/linux/irqflags.h:18,
from include/linux/spinlock.h:59,
from include/linux/swap.h:5:
include/linux/numa.h:47:19: note: previous definition of 'memory_add_physaddr_to_nid' with type 'int(u64)' {aka 'int(long long unsigned int)'}
47 | static inline int memory_add_physaddr_to_nid(u64 start)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/arm64/include/asm/sparsemem.h:34:29: error: redefinition of 'phys_to_target_node'
34 | #define phys_to_target_node phys_to_target_node
| ^~~~~~~~~~~~~~~~~~~
arch/arm64/mm/init.c:75:5: note: in expansion of macro 'phys_to_target_node'
75 | int phys_to_target_node(phys_addr_t start)
| ^~~~~~~~~~~~~~~~~~~
include/linux/numa.h:51:19: note: previous definition of 'phys_to_target_node' with type 'int(phys_addr_t)' {aka 'int(long long unsigned int)'}
51 | static inline int phys_to_target_node(u64 start)
| ^~~~~~~~~~~~~~~~~~~
vim +/phys_to_target_node +34 arch/arm64/include/asm/sparsemem.h
30
31 extern int memory_add_physaddr_to_nid(u64 addr);
32 #define memory_add_physaddr_to_nid memory_add_physaddr_to_nid
33 extern int phys_to_target_node(phys_addr_t start);
> 34 #define phys_to_target_node phys_to_target_node
35
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-15 17:16 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=202405160145.lGsTS81g-lkp@intel.com \
--to=lkp@intel.com \
--cc=dan.j.williams@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).