All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH] revocable: fix missing module license and description
Date: Tue, 20 Jan 2026 16:17:05 +0800	[thread overview]
Message-ID: <202601201432.ouoVHvm5-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: drivers/base/revocable_test.c:141:1: sparse: sparse: bad integer constant expression"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260119195141.12843-1-dakr@kernel.org>
References: <20260119195141.12843-1-dakr@kernel.org>
TO: Danilo Krummrich <dakr@kernel.org>
TO: gregkh@linuxfoundation.org
TO: rafael@kernel.org
TO: tzungbi@kernel.org
TO: broonie@kernel.org
CC: linux-kernel@vger.kernel.org
CC: Danilo Krummrich <dakr@kernel.org>

Hi Danilo,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 744905705113a6ab4c38127f18cc0d71594cfaec]

url:    https://github.com/intel-lab-lkp/linux/commits/Danilo-Krummrich/revocable-fix-missing-module-license-and-description/20260120-035657
base:   744905705113a6ab4c38127f18cc0d71594cfaec
patch link:    https://lore.kernel.org/r/20260119195141.12843-1-dakr%40kernel.org
patch subject: [PATCH] revocable: fix missing module license and description
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
config: openrisc-randconfig-r134-20260120 (https://download.01.org/0day-ci/archive/20260120/202601201432.ouoVHvm5-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260120/202601201432.ouoVHvm5-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/202601201432.ouoVHvm5-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/base/revocable_test.c:141:1: sparse: sparse: bad integer constant expression
   drivers/base/revocable_test.c:141:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
   drivers/base/revocable_test.c:142:1: sparse: sparse: bad integer constant expression
   drivers/base/revocable_test.c:142:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
   drivers/base/revocable_test.c:142:1: sparse: sparse: bad integer constant expression
   drivers/base/revocable_test.c:142:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"

vim +141 drivers/base/revocable_test.c

6a15cba130af06 Danilo Krummrich 2026-01-19  140  
6a15cba130af06 Danilo Krummrich 2026-01-19 @141  MODULE_DESCRIPTION("KUnit tests for the revocable API");

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-01-20  8:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20  8:17 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-19 19:51 [PATCH] revocable: fix missing module license and description Danilo Krummrich
2026-01-20  6:04 ` Tzung-Bi Shih
2026-01-20 10:02 ` Danilo Krummrich

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=202601201432.ouoVHvm5-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.