From: David Miller <davem@davemloft.net>
To: thomas.lendacky@amd.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/12] amd-xgbe: AMD XGBE driver updates 2018-05-21
Date: Wed, 23 May 2018 16:33:18 -0400 (EDT) [thread overview]
Message-ID: <20180523.163318.57150945055147704.davem@davemloft.net> (raw)
In-Reply-To: <20180523163802.31625.76572.stgit@tlendack-t1.amdoffice.net>
From: Tom Lendacky <thomas.lendacky@amd.com>
Date: Wed, 23 May 2018 11:38:02 -0500
> The following updates are included in this driver update series:
>
> - Fix the debug output for the max channels count
> - Read (once) and save the port property registers during probe
> - Remove the use of the comm_owned field
> - Remove unused SFP diagnostic support indicator field
> - Add ethtool --module-info support
> - Add ethtool --show-ring/--set-ring support
> - Update the driver in preparation for ethtool --set-channels support
> - Add ethtool --show-channels/--set-channels support
> - Update the driver to always perform link training in KR mode
> - Advertise FEC support when using a KR re-driver
> - Update the BelFuse quirk to now support SGMII
> - Improve 100Mbps auto-negotiation for BelFuse parts
>
> This patch series is based on net-next.
>
> ---
>
> Changes since v1:
> - Update the --set-channels support to the use of the combined, rx and
> tx options as specified in the ethtool man page (in other words, don't
> create combined channels based on the min of the tx and rx channels
> specified).
Series applied, thanks Tom.
prev parent reply other threads:[~2018-05-23 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 16:38 [PATCH net-next v2 00/12] amd-xgbe: AMD XGBE driver updates 2018-05-21 Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 01/12] amd-xgbe: Fix debug output of max channel counts Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 02/12] amd-xgbe: Read and save the port property registers during probe Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 03/12] amd-xgbe: Remove use of comm_owned field Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 04/12] amd-xgbe: Remove field that indicates SFP diagnostic support Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 05/12] amd-xgbe: Add ethtool support to retrieve SFP module info Tom Lendacky
2018-05-23 16:38 ` [PATCH net-next v2 06/12] amd-xgbe: Add ethtool show/set ring parameter support Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 07/12] amd-xgbe: Prepare for ethtool set-channel support Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 08/12] amd-xgbe: Add ethtool show/set channels support Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 09/12] amd-xgbe: Always attempt link training in KR mode Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 10/12] amd-xgbe: Advertise FEC support with the KR re-driver Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 11/12] amd-xgbe: Update the BelFuse quirk to support SGMII Tom Lendacky
2018-05-23 16:39 ` [PATCH net-next v2 12/12] amd-xgbe: Improve SFP 100Mbps auto-negotiation Tom Lendacky
2018-05-23 20:33 ` 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=20180523.163318.57150945055147704.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=thomas.lendacky@amd.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