From: kernel test robot <lkp@intel.com>
To: Neil Armstrong <neil.armstrong@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Bjorn Andersson <andersson@kernel.org>
Subject: drivers/usb/typec/ucsi/ucsi_glink.c:258:2-3: Unneeded semicolon
Date: Mon, 8 Jan 2024 14:59:54 +0800 [thread overview]
Message-ID: <202401081453.4Ff5FBfw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
commit: 62b5412b1f4afab27d8df90ddcabb8e1e11a00ad usb: typec: ucsi: add PMIC Glink UCSI driver
date: 10 months ago
config: i386-randconfig-052-20240106 (https://download.01.org/0day-ci/archive/20240108/202401081453.4Ff5FBfw-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
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/202401081453.4Ff5FBfw-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> drivers/usb/typec/ucsi/ucsi_glink.c:258:2-3: Unneeded semicolon
vim +258 drivers/usb/typec/ucsi/ucsi_glink.c
242
243 static void pmic_glink_ucsi_callback(const void *data, size_t len, void *priv)
244 {
245 struct pmic_glink_ucsi *ucsi = priv;
246 const struct pmic_glink_hdr *hdr = data;
247
248 switch (hdr->opcode) {
249 case UC_UCSI_READ_BUF_REQ:
250 pmic_glink_ucsi_read_ack(ucsi, data, len);
251 break;
252 case UC_UCSI_WRITE_BUF_REQ:
253 pmic_glink_ucsi_write_ack(ucsi, data, len);
254 break;
255 case UC_UCSI_USBC_NOTIFY_IND:
256 schedule_work(&ucsi->notify_work);
257 break;
> 258 };
259 }
260
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-08 7:01 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=202401081453.4Ff5FBfw-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--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