From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: lib/tests/string_kunit.c:866:9: sparse: sparse: not a function __func
Date: Wed, 24 Jun 2026 07:54:38 +0800 [thread overview]
Message-ID: <202606240752.RIfKz4Go-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/tests/string_kunit.c:866:9: sparse: sparse: not a function __func"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Feng Jiang <jiangfeng@kylinos.cn>
CC: Paul Walmsley <pjw@kernel.org>
CC: Kees Cook <kees@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 558ef39aeb9a089a6be9dda8413b0b9d42e843ea
commit: 0020240a431187628e2636284023e63b9b7a2aa1 lib/string_kunit: add performance benchmark for strlen()
date: 3 months ago
:::::: branch date: 57 minutes ago
:::::: commit date: 3 months ago
config: s390-randconfig-r123-20260623 (https://download.01.org/0day-ci/archive/20260624/202606240752.RIfKz4Go-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606240752.RIfKz4Go-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
| Fixes: 0020240a4311 ("lib/string_kunit: add performance benchmark for strlen()")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202606240752.RIfKz4Go-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
lib/tests/string_kunit.c:866:9: sparse: sparse: undefined identifier 'strlen'
lib/tests/string_kunit.c:866:9: sparse: sparse: undefined identifier 'strlen'
>> lib/tests/string_kunit.c:866:9: sparse: sparse: not a function __func
>> lib/tests/string_kunit.c:866:9: sparse: sparse: not a function __func
vim +866 lib/tests/string_kunit.c
0020240a431187 Feng Jiang 2026-04-03 863
0020240a431187 Feng Jiang 2026-04-03 864 static void string_bench_strlen(struct kunit *test)
0020240a431187 Feng Jiang 2026-04-03 865 {
0020240a431187 Feng Jiang 2026-04-03 @866 STRING_BENCH_BUF(test, buf, len, strlen, buf);
0020240a431187 Feng Jiang 2026-04-03 867 }
0020240a431187 Feng Jiang 2026-04-03 868
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-06-23 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 23:54 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-02 9:53 lib/tests/string_kunit.c:866:9: sparse: sparse: not a function __func kernel test robot
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=202606240752.RIfKz4Go-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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