From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: [PATCH] rte_rib6: fix references to rte_rib
Date: Wed, 22 Jun 2022 13:41:28 -0700 [thread overview]
Message-ID: <20220622204129.404074-1-stephen@networkplumber.org> (raw)
The comments in rte_rib6 were cut-and-pasted from rte_rib
and because of that some references to rte_rib_node were
not updated.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/rib/rte_rib6.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/rib/rte_rib6.h b/lib/rib/rte_rib6.h
index fa8e9bf7327b..36a79ae2accb 100644
--- a/lib/rib/rte_rib6.h
+++ b/lib/rib/rte_rib6.h
@@ -39,12 +39,12 @@ struct rte_rib6_node;
/** RIB configuration structure */
struct rte_rib6_conf {
/**
- * Size of extension block inside rte_rib_node.
+ * Size of extension block inside rte_rib6_node.
* This space could be used to store additional user
* defined data.
*/
size_t ext_sz;
- /* size of rte_rib_node's pool */
+ /* size of rte_rib6_node's pool */
int max_nodes;
};
@@ -306,7 +306,7 @@ rte_rib6_create(const char *name, int socket_id,
* Find an existing RIB object and return a pointer to it.
*
* @param name
- * Name of the rib object as passed to rte_rib_create()
+ * Name of the rib object as passed to rte_rib6_create()
* @return
* Pointer to RIB object on success
* NULL otherwise with rte_errno indicating reason for failure.
--
2.35.1
next reply other threads:[~2022-06-22 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 20:41 Stephen Hemminger [this message]
2022-06-24 11:49 ` Medvedkin, Vladimir
2022-06-26 10:11 ` Thomas Monjalon
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=20220622204129.404074-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@intel.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).