From: "lipeng (Y)" <lipeng321@huawei.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <yisen.zhuang@huawei.com>,
<salil.mehta@huawei.com>
Subject: Re: [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver
Date: Wed, 8 Nov 2017 15:17:09 +0800 [thread overview]
Message-ID: <d6b26c51-0086-3c36-4321-ac13b2c770c0@huawei.com> (raw)
In-Reply-To: <1510126279-31751-1-git-send-email-lipeng321@huawei.com>
please ignore this patch-set.
I should remove "{topost}" from the subject.
sorry for that, I will resend the patch-set.
On 2017/11/8 15:31, Lipeng wrote:
> This patch-set introduces some bug fixes and code improvements.
> As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using
> GENMASK in hns3 driver}, which exists in net-next, not exists in net, so
> push this serise to nex-next.
>
> Fuyun Liang (2):
> {topost} net: hns3: fix a bug when getting phy address from NCL_config
> file
> {topost} net: hns3: cleanup mac auto-negotiation state query in
> hclge_update_speed_duplex
>
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 2 +-
> drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 13 +------------
> 2 files changed, 2 insertions(+), 13 deletions(-)
>
next prev parent reply other threads:[~2017-11-08 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 7:31 [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver Lipeng
2017-11-08 7:17 ` lipeng (Y) [this message]
2017-11-08 7:31 ` [PATCH net-next 1/2] {topost} net: hns3: fix a bug when getting phy address from NCL_config file Lipeng
2017-11-08 7:31 ` [PATCH net-next 2/2] {topost} net: hns3: cleanup mac auto-negotiation state query in hclge_update_speed_duplex Lipeng
2017-11-08 7:52 [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver Lipeng
2017-11-11 6:20 ` 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=d6b26c51-0086-3c36-4321-ac13b2c770c0@huawei.com \
--to=lipeng321@huawei.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@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).