From: Danielle Ratson <danieller@mellanox.com>
To: netdev@vger.kernel.org
Cc: mkubecek@suse.cz, f.fainelli@gmail.com, kuba@kernel.org,
andrew@lunn.ch, mlxsw@nvidia.com,
Danielle Ratson <danieller@nvidia.com>
Subject: [PATCH ethtool 5/5] man: Add man page for setting lanes parameter
Date: Wed, 6 Jan 2021 15:10:06 +0200 [thread overview]
Message-ID: <20210106131006.2110613-6-danieller@mellanox.com> (raw)
In-Reply-To: <20210106131006.2110613-1-danieller@mellanox.com>
From: Danielle Ratson <danieller@nvidia.com>
Lanes parameter was added for setting using ethtool.
Update the man page to include the new parameter.
Signed-off-by: Danielle Ratson <danieller@nvidia.com>
---
ethtool.8.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/ethtool.8.in b/ethtool.8.in
index ba4e245..fe49b66 100644
--- a/ethtool.8.in
+++ b/ethtool.8.in
@@ -251,6 +251,7 @@ ethtool \- query or control network driver and hardware settings
.B ethtool \-s
.I devname
.BN speed
+.BN lanes
.B2 duplex half full
.B4 port tp aui bnc mii fibre da
.B3 mdix auto on off
@@ -685,6 +686,9 @@ Set speed in Mb/s.
.B ethtool
with just the device name as an argument will show you the supported device speeds.
.TP
+.BI lanes \ N
+Set number of lanes.
+.TP
.A2 duplex half full
Sets full or half duplex mode.
.TP
--
2.26.2
prev parent reply other threads:[~2021-01-06 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 13:10 [PATCH ethtool 0/5] Extend uAPI with lanes parameter Danielle Ratson
2021-01-06 13:10 ` [PATCH ethtool 1/5] ethtool: Extend ethtool link modes settings uAPI with lanes Danielle Ratson
2021-01-06 13:10 ` [PATCH ethtool 2/5] netlink: settings: Add netlink support for lanes parameter Danielle Ratson
2021-01-06 13:10 ` [PATCH ethtool 3/5] netlink: settings: Expose the number of lanes in use Danielle Ratson
2021-01-06 13:10 ` [PATCH ethtool 4/5] shell-completion: Add completion for lanes Danielle Ratson
2021-01-06 13:10 ` Danielle Ratson [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=20210106131006.2110613-6-danieller@mellanox.com \
--to=danieller@mellanox.com \
--cc=andrew@lunn.ch \
--cc=danieller@nvidia.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
/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).