From: Andrew Lunn <andrew@lunn.ch>
To: zhengbin <zhengbin13@huawei.com>
Cc: f.fainelli@gmail.com, hkallweit1@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: phy: dp83869: Remove unneeded semicolon
Date: Sun, 15 Dec 2019 00:11:06 +0100 [thread overview]
Message-ID: <20191214231106.GC6314@lunn.ch> (raw)
In-Reply-To: <1576318644-38066-1-git-send-email-zhengbin13@huawei.com>
On Sat, Dec 14, 2019 at 06:17:24PM +0800, zhengbin wrote:
> Fixes coccicheck warning:
>
> drivers/net/phy/dp83869.c:337:2-3: Unneeded semicolon
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: zhengbin <zhengbin13@huawei.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-12-14 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 10:17 [PATCH net-next] net: phy: dp83869: Remove unneeded semicolon zhengbin
2019-12-14 23:11 ` Andrew Lunn [this message]
2019-12-15 0:12 ` Jakub Kicinski
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=20191214231106.GC6314@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=zhengbin13@huawei.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).