From: Kory Maincent <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Michal Kubecek <mkubecek@suse.cz>
Cc: Kyle Swenson <kyle.swenson@est.tech>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Kory Maincent <kory.maincent@bootlin.com>
Subject: [PATCH ethtool-next 2/3] ethtool.8: Fix small documentation nit
Date: Thu, 12 Sep 2024 11:20:03 +0200 [thread overview]
Message-ID: <20240912-feature_poe_power_cap-v1-2-499e3dd996d7@bootlin.com> (raw)
In-Reply-To: <20240912-feature_poe_power_cap-v1-0-499e3dd996d7@bootlin.com>
From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
Remove useless .RE macro call.
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
ethtool.8.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/ethtool.8.in b/ethtool.8.in
index bf8af57..3b4df42 100644
--- a/ethtool.8.in
+++ b/ethtool.8.in
@@ -1809,7 +1809,6 @@ status depend on internal PSE state machine and automatic PD classification
support. It corresponds to IEEE 802.3-2022 30.9.1.1.5
(aPSEPowerDetectionStatus) with potential values being
.B disabled, searching, delivering power, test, fault, other fault
-.RE
.RE
.TP
--
2.34.1
next prev parent reply other threads:[~2024-09-12 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 9:20 [PATCH ethtool-next 0/3] Add support for new features in C33 PSE Kory Maincent
2024-09-12 9:20 ` [PATCH ethtool-next 1/3] ethtool: pse-pd: Expand C33 PSE with several new features Kory Maincent
2024-09-12 9:20 ` Kory Maincent [this message]
2024-09-12 9:20 ` [PATCH ethtool-next 3/3] ethtool.8: Add documentation for new C33 PSE features Kory Maincent
2024-09-16 20:10 ` [PATCH ethtool-next 0/3] Add support for new features in C33 PSE patchwork-bot+netdevbpf
2024-09-16 20:11 ` Michal Kubecek
2024-09-17 8:12 ` Kory Maincent
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=20240912-feature_poe_power_cap-v1-2-499e3dd996d7@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kyle.swenson@est.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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