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-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Benjamin Berg <benjamin.berg@intel.com>,
Maxime Ripard <maxime@cerno.tech>
Subject: lib/kunit/executor_test.c:138:4: warning: cast from 'void (*)(const void *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts to incompatible function type
Date: Mon, 11 Sep 2023 14:19:25 +0800 [thread overview]
Message-ID: <202309111413.inYPK4PP-lkp@intel.com> (raw)
Hi David,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
commit: 00e63f8afcfc6bf93d75141c51d35e8a40e86363 kunit: executor_test: Use kunit_add_action()
date: 4 months ago
config: x86_64-randconfig-013-20230909 (https://download.01.org/0day-ci/archive/20230911/202309111413.inYPK4PP-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): (https://download.01.org/0day-ci/archive/20230911/202309111413.inYPK4PP-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/202309111413.inYPK4PP-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from lib/kunit/executor.c:223:
>> lib/kunit/executor_test.c:138:4: warning: cast from 'void (*)(const void *)' to 'kunit_action_t *' (aka 'void (*)(void *)') converts to incompatible function type [-Wcast-function-type-strict]
(kunit_action_t *)kfree,
^~~~~~~~~~~~~~~~~~~~~~~
1 warning 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-09-11 6:20 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=202309111413.inYPK4PP-lkp@intel.com \
--to=lkp@intel.com \
--cc=benjamin.berg@intel.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.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