From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH v3 3/9] clk: realtek: Introduce a common probe()
Date: Fri, 23 Jan 2026 02:31:25 +0800 [thread overview]
Message-ID: <202601230204.TiGCq9lc-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: drivers/clk/realtek/common.c:63:1: sparse: sparse: bad integer constant expression"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260122110857.12995-4-eleanor.lin@realtek.com>
References: <20260122110857.12995-4-eleanor.lin@realtek.com>
TO: "Yu-Chun Lin" <eleanor.lin@realtek.com>
TO: mturquette@baylibre.com
TO: sboyd@kernel.org
TO: robh@kernel.org
TO: krzk+dt@kernel.org
TO: conor+dt@kernel.org
TO: p.zabel@pengutronix.de
TO: cylee12@realtek.com
TO: jyanchou@realtek.com
CC: devicetree@vger.kernel.org
CC: linux-clk@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: james.tai@realtek.com
CC: cy.huang@realtek.com
CC: stanley_chang@realtek.com
CC: eleanor.lin@realtek.com
Hi Yu-Chun,
kernel test robot noticed the following build warnings:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on linus/master v6.19-rc6 next-20260121]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Yu-Chun-Lin/dt-bindings-clock-Add-Realtek-RTD1625-Clock-Reset-Controller/20260122-194325
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
patch link: https://lore.kernel.org/r/20260122110857.12995-4-eleanor.lin%40realtek.com
patch subject: [PATCH v3 3/9] clk: realtek: Introduce a common probe()
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: powerpc-randconfig-r123-20260122 (https://download.01.org/0day-ci/archive/20260123/202601230204.TiGCq9lc-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601230204.TiGCq9lc-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/202601230204.TiGCq9lc-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/clk/realtek/common.c:63:1: sparse: sparse: bad integer constant expression
drivers/clk/realtek/common.c:63:1: sparse: sparse: static assertion failed: "MODULE_INFO(description, ...) contains embedded NUL byte"
drivers/clk/realtek/common.c:64:1: sparse: sparse: bad integer constant expression
drivers/clk/realtek/common.c:64:1: sparse: sparse: static assertion failed: "MODULE_INFO(file, ...) contains embedded NUL byte"
drivers/clk/realtek/common.c:64:1: sparse: sparse: bad integer constant expression
drivers/clk/realtek/common.c:64:1: sparse: sparse: static assertion failed: "MODULE_INFO(license, ...) contains embedded NUL byte"
vim +63 drivers/clk/realtek/common.c
3c88898c54673d Cheng-Yu Lee 2026-01-22 62
3c88898c54673d Cheng-Yu Lee 2026-01-22 @63 MODULE_DESCRIPTION("Realtek clock infrastructure");
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-22 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 18:31 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-22 11:08 [PATCH v3 0/9] clk: realtek: Add RTD1625 Clock Support Yu-Chun Lin
2026-01-22 11:08 ` [PATCH v3 3/9] clk: realtek: Introduce a common probe() Yu-Chun Lin
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=202601230204.TiGCq9lc-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.