From: kbuild test robot <lkp@intel.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org
Subject: [net-next:master 54/321] drivers/net/phy/dp83867.c:363:2-3: Unneeded semicolon
Date: Tue, 24 Mar 2020 03:51:39 +0800 [thread overview]
Message-ID: <202003240333.9w4m8TaM%lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 09984483db080b541c8242d846c30bc1e6a194e1
commit: cd26d72d4d43175cec8c10bed4df7f21ac5316b3 [54/321] net: phy: dp83867: Add speed optimization feature
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
coccinelle warnings: (new ones prefixed by >>)
>> drivers/net/phy/dp83867.c:363:2-3: Unneeded semicolon
drivers/net/phy/dp83867.c:398:2-3: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2020-03-23 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 19:51 kbuild test robot [this message]
2020-03-23 19:51 ` [PATCH] net: phy: dp83867: fix semicolon.cocci warnings kbuild test robot
2020-03-23 20:00 ` Andrew Lunn
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=202003240333.9w4m8TaM%lkp@intel.com \
--to=lkp@intel.com \
--cc=dmurphy@ti.com \
--cc=kbuild-all@lists.01.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).