From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 136/153] drivers/usb/typec/ucsi/cros_ec_ucsi.c:127:24: sparse: sparse: symbol 'cros_ucsi_ops' was not declared. Should it be static?
Date: Sun, 28 Apr 2024 03:37:46 +0800 [thread overview]
Message-ID: <202404280306.To66RR4B-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 7ec7b4b9d284b739801688bc0d8d02ead80edc06
commit: c4305a040e64e8f28aef41db921b3de50d62e902 [136/153] CHROMIUM: usb: typec: Implement UCSI driver for ChromeOS
config: x86_64-randconfig-122-20240428 (https://download.01.org/0day-ci/archive/20240428/202404280306.To66RR4B-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240428/202404280306.To66RR4B-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/202404280306.To66RR4B-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/usb/typec/ucsi/cros_ec_ucsi.c:127:24: sparse: sparse: symbol 'cros_ucsi_ops' was not declared. Should it be static?
drivers/usb/typec/ucsi/cros_ec_ucsi.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/umh.h, include/linux/kmod.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
vim +/cros_ucsi_ops +127 drivers/usb/typec/ucsi/cros_ec_ucsi.c
126
> 127 struct ucsi_operations cros_ucsi_ops = {
128 .read = cros_ucsi_read,
129 .async_write = cros_ucsi_async_write,
130 .sync_write = cros_ucsi_sync_write,
131 };
132
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-27 19:37 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=202404280306.To66RR4B-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.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 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.