From: Chiara Meiohas <cmeioahs@nvidia.com>
To: <dsahern@gmail.com>, <leonro@nvidia.com>
Cc: <linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
<jgg@nvidia.com>, <stephen@networkplumber.org>,
Chiara Meiohas <cmeiohas@nvidia.com>,
"Mark Bloch" <mbloch@nvidia.com>
Subject: [PATCH v2 iproute2-next 3/5] rdma: Fix typo in rdma-link man page
Date: Thu, 7 Nov 2024 10:02:46 +0200 [thread overview]
Message-ID: <20241107080248.2028680-4-cmeioahs@nvidia.com> (raw)
In-Reply-To: <20241107080248.2028680-1-cmeioahs@nvidia.com>
From: Chiara Meiohas <cmeiohas@nvidia.com>
Signed-off-by: Chiara Meiohas <cmeiohas@nvidia.com>
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
---
man/man8/rdma-link.8 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man8/rdma-link.8 b/man/man8/rdma-link.8
index 32f80228..5e4a5307 100644
--- a/man/man8/rdma-link.8
+++ b/man/man8/rdma-link.8
@@ -6,7 +6,7 @@ rdma-link \- rdma link configuration
.ad l
.in +8
.ti -8
-.B devlink
+.B rdma
.RI "[ " OPTIONS " ]"
.B link
.RI " { " COMMAND " | "
--
2.44.0
next prev parent reply other threads:[~2024-11-07 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 8:02 [PATCH v2 iproute2-next 0/5] Add RDMA monitor support Chiara Meiohas
2024-11-07 8:02 ` [PATCH v2 iproute2-next 1/5] rdma: Add support for rdma monitor Chiara Meiohas
2024-11-09 17:34 ` David Ahern
2024-11-11 8:01 ` Chiara Meiohas
2024-11-07 8:02 ` [PATCH v2 iproute2-next 2/5] rdma: Expose whether RDMA monitoring is supported Chiara Meiohas
2024-11-07 8:02 ` Chiara Meiohas [this message]
2024-11-07 8:02 ` [PATCH v2 iproute2-next 4/5] rdma: update uapi headers Chiara Meiohas
2024-11-07 8:02 ` [PATCH v2 iproute2-next 5/5] rdma: Add IB device and net device rename events Chiara Meiohas
2024-11-07 16:24 ` [PATCH v2 iproute2-next 0/5] Add RDMA monitor support Stephen Hemminger
2024-11-07 22:37 ` Chiara Meiohas
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=20241107080248.2028680-4-cmeioahs@nvidia.com \
--to=cmeioahs@nvidia.com \
--cc=cmeiohas@nvidia.com \
--cc=dsahern@gmail.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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