From: kbuild test robot <fengguang.wu@intel.com>
To: Igor Plyatov <plyatov@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net:master 10/12] drivers/net/phy/smsc.c:127:3-4: Unneeded semicolon
Date: Tue, 18 Aug 2015 06:31:42 +0800 [thread overview]
Message-ID: <201508180640.tFfxPCXM%fengguang.wu@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
head: af19e68683ba9c29e778d0f8be5be61a0ebb4166
commit: 776829de90c5972895db398993ddfa9417ff8b01 [10/12] net: phy: workaround for buggy cable detection by LAN8700 after cable plugging
coccinelle warnings: (new ones prefixed by >>)
>> drivers/net/phy/smsc.c:127:3-4: Unneeded semicolon
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2015-08-17 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 22:31 kbuild test robot [this message]
2015-08-17 22:31 ` [PATCH] net: phy: fix semicolon.cocci warnings kbuild test robot
2015-08-17 22:53 ` David Miller
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=201508180640.tFfxPCXM%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=plyatov@gmail.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;
as well as URLs for NNTP newsgroup(s).