From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 315/342] mm/slub.c:1038:17: error: implicit declaration of function '__memset'; did you mean 'memset'?
Date: Fri, 15 Dec 2023 11:03:18 -0800 [thread overview]
Message-ID: <20231215110318.547feca5775b9b15bd823c5d@linux-foundation.org> (raw)
In-Reply-To: <202312151925.c1R7UpLE-lkp@intel.com>
On Fri, 15 Dec 2023 19:23:07 +0800 kernel test robot <lkp@intel.com> wrote:
> ree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 3271cacfede84a7e27d318fdf12fbeb7cab7b305
> commit: 082b07014f97afe25e73493a58f21b45c2742cd7 [315/342] kmsan: support SLAB_POISON
> config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20231215/202312151925.c1R7UpLE-lkp@intel.com/config)
> compiler: arc-elf-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231215/202312151925.c1R7UpLE-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/202312151925.c1R7UpLE-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> mm/slub.c: In function 'init_object':
> >> mm/slub.c:1038:17: error: implicit declaration of function '__memset'; did you mean 'memset'? [-Werror=implicit-function-declaration]
> 1038 | __memset(p - s->red_left_pad, val, s->red_left_pad);
> | ^~~~~~~~
> | memset
> cc1: some warnings being treated as errors
Not all architectures implement __memset().
I'll disable the series for now, thanks.
prev parent reply other threads:[~2023-12-15 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 11:23 kernel test robot
2023-12-15 19:03 ` Andrew Morton [this message]
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=20231215110318.547feca5775b9b15bd823c5d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iii@linux.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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