From: kernel test robot <lkp@intel.com>
To: RD Babiera <rdbabiera@google.com>
Cc: oe-kbuild-all@lists.linux.dev, badhri@google.com,
heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
RD Babiera <rdbabiera@google.com>
Subject: Re: [PATCH v1] usb: typec: tcpm: implement retry mechanism for Discover Identity VDMs
Date: Tue, 16 Jun 2026 14:03:08 +0800 [thread overview]
Message-ID: <202606161310.GCXb2ogf-lkp@intel.com> (raw)
In-Reply-To: <20260615194923.4192117-2-rdbabiera@google.com>
Hi RD,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 511e746700ee6e93104d061a87743906128ab709]
url: https://github.com/intel-lab-lkp/linux/commits/RD-Babiera/usb-typec-tcpm-implement-retry-mechanism-for-Discover-Identity-VDMs/20260616-035226
base: 511e746700ee6e93104d061a87743906128ab709
patch link: https://lore.kernel.org/r/20260615194923.4192117-2-rdbabiera%40google.com
patch subject: [PATCH v1] usb: typec: tcpm: implement retry mechanism for Discover Identity VDMs
config: loongarch-randconfig-r133-20260616 (https://download.01.org/0day-ci/archive/20260616/202606161310.GCXb2ogf-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project e19d1f51a2c80b63cd8ca95bcc757b7077112808)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260616/202606161310.GCXb2ogf-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/202606161310.GCXb2ogf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/usb/typec/tcpm/tcpm.c:286:12: sparse: sparse: symbol 'vdm_discovery_state_strings' was not declared. Should it be static?
vim +/vdm_discovery_state_strings +286 drivers/usb/typec/tcpm/tcpm.c
285
> 286 const char *vdm_discovery_state_strings[] = {
287 [VDM_DISCOVERY_UNKNOWN] = "VDM_DISCOVERY_UNKNOWN",
288 [VDM_DISCOVERY_PARTNER_IDENT] = "VDM_DISCOVERY_PARTNER_IDENT",
289 [VDM_DISCOVERY_CABLE_IDENT] = "VDM_DISCOVERY_CABLE_IDENT",
290 [VDM_DISCOVERY_PARTNER_SVIDS] = "VDM_DISCOVERY_PARTNER_SVIDS",
291 [VDM_DISCOVERY_PARTNER_MODES] = "VDM_DISCOVERY_PARTNER_MODES",
292 [VDM_DISCOVERY_CABLE_SVIDS] = "VDM_DISCOVERY_CABLE_SVIDS",
293 [VDM_DISCOVERY_CABLE_MODES] = "VDM_DISCOVERY_CABLE_MODES",
294 [VDM_DISCOVERY_COMPLETE] = "VDM_DISCOVERY_COMPLETE",
295 };
296
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-06-16 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 19:49 [PATCH v1] usb: typec: tcpm: implement retry mechanism for Discover Identity VDMs RD Babiera
2026-06-16 6:03 ` kernel test robot [this message]
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=202606161310.GCXb2ogf-lkp@intel.com \
--to=lkp@intel.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdbabiera@google.com \
/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