From: kernel test robot <lkp@intel.com>
To: Maxwell Bland <mbland@motorola.com>,
linux-arm-kernel@lists.infradead.org
Cc: oe-kbuild-all@lists.linux.dev, gregkh@linuxfoundation.org,
agordeev@linux.ibm.com, akpm@linux-foundation.org,
andreyknvl@gmail.com, andrii@kernel.org, aneesh.kumar@kernel.org,
aou@eecs.berkeley.edu, ardb@kernel.org, arnd@arndb.de,
ast@kernel.org, borntraeger@linux.ibm.com, bpf@vger.kernel.org,
brauner@kernel.org, catalin.marinas@arm.com,
christophe.leroy@csgroup.eu, cl@linux.com, daniel@iogearbox.net,
dave.hansen@linux.intel.com, david@redhat.com, dennis@kernel.org,
dvyukov@google.com, glider@google.com, gor@linux.ibm.com,
guoren@kernel.org, haoluo@google.com, hca@linux.ibm.com,
hch@infradead.org, john.fastabend@gmail.com, jolsa@kernel.org
Subject: Re: [PATCH 1/4] mm/vmalloc: allow arch-specific vmalloc_node overrides
Date: Thu, 22 Feb 2024 02:25:09 +0800 [thread overview]
Message-ID: <202402220229.5xZWdZBK-lkp@intel.com> (raw)
In-Reply-To: <20240220203256.31153-2-mbland@motorola.com>
Hi Maxwell,
kernel test robot noticed the following build errors:
[auto build test ERROR on b401b621758e46812da61fa58a67c3fd8d91de0d]
url: https://github.com/intel-lab-lkp/linux/commits/Maxwell-Bland/mm-vmalloc-allow-arch-specific-vmalloc_node-overrides/20240221-043458
base: b401b621758e46812da61fa58a67c3fd8d91de0d
patch link: https://lore.kernel.org/r/20240220203256.31153-2-mbland%40motorola.com
patch subject: [PATCH 1/4] mm/vmalloc: allow arch-specific vmalloc_node overrides
config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20240222/202402220229.5xZWdZBK-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240222/202402220229.5xZWdZBK-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/202402220229.5xZWdZBK-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/nommu.c:160:7: error: conflicting types for '__vmalloc_node'; have 'void *(long unsigned int, long unsigned int, gfp_t, int, const void *)' {aka 'void *(long unsigned int, long unsigned int, unsigned int, int, const void *)'}
160 | void *__vmalloc_node(unsigned long size, unsigned long align, gfp_t gfp_mask,
| ^~~~~~~~~~~~~~
In file included from include/asm-generic/io.h:994,
from arch/m68k/include/asm/io.h:14,
from arch/m68k/include/asm/pgtable_no.h:14,
from arch/m68k/include/asm/pgtable.h:6,
from include/linux/pgtable.h:6,
from include/linux/mm.h:29,
from mm/nommu.c:20:
include/linux/vmalloc.h:152:7: note: previous declaration of '__vmalloc_node' with type 'void *(long unsigned int, long unsigned int, gfp_t, long unsigned int, int, const void *)' {aka 'void *(long unsigned int, long unsigned int, unsigned int, long unsigned int, int, const void *)'}
152 | void *__vmalloc_node(unsigned long size, unsigned long align, gfp_t gfp_mask,
| ^~~~~~~~~~~~~~
vim +160 mm/nommu.c
041de93ff86fc5 Christoph Hellwig 2020-06-01 159
2b9059489c839e Christoph Hellwig 2020-06-01 @160 void *__vmalloc_node(unsigned long size, unsigned long align, gfp_t gfp_mask,
2b9059489c839e Christoph Hellwig 2020-06-01 161 int node, const void *caller)
a7c3e901a46ff5 Michal Hocko 2017-05-08 162 {
2b9059489c839e Christoph Hellwig 2020-06-01 163 return __vmalloc(size, gfp_mask);
a7c3e901a46ff5 Michal Hocko 2017-05-08 164 }
a7c3e901a46ff5 Michal Hocko 2017-05-08 165
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-21 18:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 20:32 [PATCH 0/4] arm64: mm: support dynamic vmalloc/pmd configuration Maxwell Bland
2024-02-20 20:32 ` [PATCH 1/4] mm/vmalloc: allow arch-specific vmalloc_node overrides Maxwell Bland
2024-02-21 5:43 ` Christoph Hellwig
2024-02-21 7:38 ` Christophe Leroy
2024-02-21 6:59 ` Christophe Leroy
2024-02-21 17:19 ` Maxwell Bland
2024-02-21 18:25 ` kernel test robot [this message]
2024-02-20 20:32 ` [PATCH 2/4] mm: pgalloc: support address-conditional pmd allocation Maxwell Bland
2024-02-21 7:13 ` Christophe Leroy
2024-02-21 9:27 ` David Hildenbrand
2024-02-21 15:54 ` [External] " Maxwell Bland
2024-02-21 16:57 ` kernel test robot
2024-02-21 17:08 ` kernel test robot
2024-02-20 20:32 ` [PATCH 3/4] arm64: separate code and data virtual memory allocation Maxwell Bland
2024-02-21 7:20 ` Christophe Leroy
2024-02-20 20:32 ` [PATCH 4/4] arm64: dynamic enforcement of pmd-level PXNTable Maxwell Bland
2024-02-21 7:32 ` [PATCH 0/4] arm64: mm: support dynamic vmalloc/pmd configuration Christophe Leroy
2024-02-21 17:57 ` Maxwell Bland
2024-02-21 14:50 ` Conor Dooley
2024-02-21 15:42 ` [External] " Maxwell Bland
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=202402220229.5xZWdZBK-lkp@intel.com \
--to=lkp@intel.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=andrii@kernel.org \
--cc=aneesh.kumar@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dennis@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guoren@kernel.org \
--cc=haoluo@google.com \
--cc=hca@linux.ibm.com \
--cc=hch@infradead.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mbland@motorola.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