From: David Miller <davem@davemloft.net>
To: lipeng321@huawei.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, salil.mehta@huawei.com
Subject: Re: [PATCH V2 net-next 0/4] add some features to hns3 driver
Date: Mon, 22 Jan 2018 16:06:06 -0500 (EST) [thread overview]
Message-ID: <20180122.160606.1473995205840062094.davem@davemloft.net> (raw)
In-Reply-To: <1516344072-109127-1-git-send-email-lipeng321@huawei.com>
From: Peng Li <lipeng321@huawei.com>
Date: Fri, 19 Jan 2018 14:41:08 +0800
> This patchset adds some features to hns3 driver, include the support
> for ethtool command -d, -p and support for manager table.
>
> [Patch 1/4] adds support for ethtool command -d, its ops is get_regs.
> driver will send command to command queue, and get regs number and
> regs value from command queue.
> [Patch 2/4] adds manager table initialization for hardware.
> [Patch 3/4] adds support for ethtool command -p. For fiber ports, driver
> sends command to command queue, and IMP will write SGPIO regs to control
> leds.
> [Patch 4/4] adds support for net status led for fiber ports. Net status
> include port speed, total rx/tx packets and link status. Driver send
> the status to command queue, and IMP will write SGPIO to control leds.
>
> ---
> Change log:
> V1 -> V2:
> 1, fix comments from Andrew Lunn, remove the patch "net: hns3: add
> ethtool -p support for phy device".
Series applied, thanks.
prev parent reply other threads:[~2018-01-22 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 6:41 [PATCH V2 net-next 0/4] add some features to hns3 driver Peng Li
2018-01-19 6:41 ` [PATCH V2 net-next 1/4] net: hns3: add support for get_regs Peng Li
2018-01-19 6:41 ` [PATCH V2 net-next 2/4] net: hns3: add manager table initialization for hardware Peng Li
2018-01-19 6:41 ` [PATCH V2 net-next 3/4] net: hns3: add ethtool -p support for fiber port Peng Li
2018-01-19 6:41 ` [PATCH V2 net-next 4/4] net: hns3: add net status led " Peng Li
2018-01-22 21:06 ` David Miller [this message]
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=20180122.160606.1473995205840062094.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@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).