From: kernel test robot <lkp@intel.com>
To: David Gow <davidgow@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Benjamin Berg <benjamin.berg@intel.com>,
Maxime Ripard <maxime@cerno.tech>
Subject: [linux-next:master 4264/7747] lib/kunit/executor_test.c:138:4: error: cast from 'void (*)(const void *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts to incompatible function type
Date: Wed, 7 Jun 2023 15:59:14 +0800 [thread overview]
Message-ID: <202306071513.vCmugxAi-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: abbd8bb42915d9ed06df11b430bf4ecb3d8ac5ad
commit: 00e63f8afcfc6bf93d75141c51d35e8a40e86363 [4264/7747] kunit: executor_test: Use kunit_add_action()
config: riscv-randconfig-r032-20230607 (https://download.01.org/0day-ci/archive/20230607/202306071513.vCmugxAi-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=00e63f8afcfc6bf93d75141c51d35e8a40e86363
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 00e63f8afcfc6bf93d75141c51d35e8a40e86363
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash lib/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202306071513.vCmugxAi-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from lib/kunit/executor.c:223:
>> lib/kunit/executor_test.c:138:4: error: cast from 'void (*)(const void *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts to incompatible function type [-Werror,-Wcast-function-type-strict]
(kunit_action_t *)kfree,
^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +138 lib/kunit/executor_test.c
127
128 /* Use the resource API to register a call to kfree(to_free).
129 * Since we never actually use the resource, it's safe to use on const data.
130 */
131 static void kfree_at_end(struct kunit *test, const void *to_free)
132 {
133 /* kfree() handles NULL already, but avoid allocating a no-op cleanup. */
134 if (IS_ERR_OR_NULL(to_free))
135 return;
136
137 kunit_add_action(test,
> 138 (kunit_action_t *)kfree,
139 (void *)to_free);
140 }
141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-07 7:59 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=202306071513.vCmugxAi-lkp@intel.com \
--to=lkp@intel.com \
--cc=benjamin.berg@intel.com \
--cc=davidgow@google.com \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=maxime@cerno.tech \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).