From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v2 1/3] test_bitmap: extract benchmark module
Date: Wed, 24 Dec 2025 10:19:00 +0800 [thread overview]
Message-ID: <202512240906.xLkpixHL-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: lib/bitmap_benchmark.c:87:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251222-bitmap-kunit-convert-v2-1-6a61a5330eff@gmail.com>
References: <20251222-bitmap-kunit-convert-v2-1-6a61a5330eff@gmail.com>
TO: Tamir Duberstein <tamird@kernel.org>
TO: David Gow <davidgow@google.com>
TO: John Hubbard <jhubbard@nvidia.com>
TO: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: Geert Uytterhoeven <geert@linux-m68k.org>
TO: Madhavan Srinivasan <maddy@linux.ibm.com>
TO: Michael Ellerman <mpe@ellerman.id.au>
TO: Nicholas Piggin <npiggin@gmail.com>
TO: Naveen N Rao <naveen@kernel.org>
TO: Yury Norov <yury.norov@gmail.com>
TO: Rasmus Villemoes <linux@rasmusvillemoes.dk>
TO: Shuah Khan <skhan@linuxfoundation.org>
TO: Kees Cook <kees@kernel.org>
TO: Christophe Leroy <chleroy@kernel.org>
CC: Muhammad Usama Anjum <usama.anjum@collabora.com>
CC: linux-kernel@vger.kernel.org
CC: linux-m68k@lists.linux-m68k.org
CC: linuxppc-dev@lists.ozlabs.org
CC: linux-kselftest@vger.kernel.org
CC: Tamir Duberstein <tamird@gmail.com>
CC: Alexander Potapenko <glider@google.com>
Hi Tamir,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 8f0b4cce4481fb22653697cced8d0d04027cb1e8]
url: https://github.com/intel-lab-lkp/linux/commits/Tamir-Duberstein/test_bitmap-extract-benchmark-module/20251222-214306
base: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
patch link: https://lore.kernel.org/r/20251222-bitmap-kunit-convert-v2-1-6a61a5330eff%40gmail.com
patch subject: [PATCH v2 1/3] test_bitmap: extract benchmark module
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: microblaze-randconfig-r111-20251224 (https://download.01.org/0day-ci/archive/20251224/202512240906.xLkpixHL-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512240906.xLkpixHL-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/r/202512240906.xLkpixHL-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/bitmap_benchmark.c:87:1: sparse: sparse: bad integer constant expression
lib/bitmap_benchmark.c:87:1: sparse: sparse: static assertion failed: "MODULE_INFO(author, ...) contains embedded NUL byte"
lib/bitmap_benchmark.c:88:1: sparse: sparse: bad integer constant expression
lib/bitmap_benchmark.c:88:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
lib/bitmap_benchmark.c:89:1: sparse: sparse: bad integer constant expression
lib/bitmap_benchmark.c:89:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
lib/bitmap_benchmark.c:89:1: sparse: sparse: bad integer constant expression
lib/bitmap_benchmark.c:89:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +87 lib/bitmap_benchmark.c
98008eee3b7dd0 Tamir Duberstein 2025-12-22 86
98008eee3b7dd0 Tamir Duberstein 2025-12-22 @87 MODULE_AUTHOR("Alexander Potapenko <glider@google.com>");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-24 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 2:19 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-22 13:39 [PATCH v2 0/3] bitmap: convert self-test to KUnit Tamir Duberstein
2025-12-22 13:39 ` [PATCH v2 1/3] test_bitmap: extract benchmark module Tamir Duberstein
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=202512240906.xLkpixHL-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.