From: kernel test robot <lkp@intel.com>
To: Pengyu Luo <mitltlatltl@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: drivers/usb/typec/ucsi/ucsi_huawei_gaokun.c:196:30: sparse: sparse: symbol 'gaokun_ucsi_ops' was not declared. Should it be static?
Date: Thu, 05 Mar 2026 02:33:03 +0800 [thread overview]
Message-ID: <202603050203.KD4RWA00-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ecc64d2dc9ff9738d2a896beb68e02c2feaf9a02
commit: 00327d7f2c8c512c9b168daae02c8b989f79ec71 usb: typec: ucsi: add Huawei Matebook E Go ucsi driver
date: 11 months ago
config: mips-randconfig-r112-20260304 (https://download.01.org/0day-ci/archive/20260305/202603050203.KD4RWA00-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260305/202603050203.KD4RWA00-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/202603050203.KD4RWA00-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/usb/typec/ucsi/ucsi_huawei_gaokun.c:196:30: sparse: sparse: symbol 'gaokun_ucsi_ops' was not declared. Should it be static?
vim +/gaokun_ucsi_ops +196 drivers/usb/typec/ucsi/ucsi_huawei_gaokun.c
195
> 196 const struct ucsi_operations gaokun_ucsi_ops = {
197 .read_version = gaokun_ucsi_read_version,
198 .read_cci = gaokun_ucsi_read_cci,
199 .read_message_in = gaokun_ucsi_read_message_in,
200 .sync_control = ucsi_sync_control_common,
201 .async_control = gaokun_ucsi_async_control,
202 .update_connector = gaokun_ucsi_update_connector,
203 .connector_status = gaokun_ucsi_connector_status,
204 };
205
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-04 18:33 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=202603050203.KD4RWA00-lkp@intel.com \
--to=lkp@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®