From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/3] mbuf: fix a couple of doxygen comments
Date: Fri, 20 Feb 2015 12:10:52 +0000 [thread overview]
Message-ID: <1424434253-6808-3-git-send-email-sergio.gonzalez.monroy@intel.com> (raw)
In-Reply-To: <1424434253-6808-1-git-send-email-sergio.gonzalez.monroy@intel.com>
Fix a couple of doxygen comments in mbuf structure:
- seqn had no doxygen syntax.
- usr was not generating proper link to function.
Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
---
lib/librte_mbuf/rte_mbuf.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
index ace6736..32e957b 100644
--- a/lib/librte_mbuf/rte_mbuf.h
+++ b/lib/librte_mbuf/rte_mbuf.h
@@ -286,11 +286,11 @@ struct rte_mbuf {
PKT_RX_FDIR_* flag in ol_flags. */
} fdir; /**< Filter identifier if FDIR enabled */
uint32_t sched; /**< Hierarchical scheduler */
- uint32_t usr; /**< User defined tags. See @rte_distributor_process */
+ uint32_t usr; /**< User defined tags. See rte_distributor_process() */
} hash; /**< hash information */
- /* sequence number - field used in distributor and reorder library */
uint32_t seqn;
+ /**< Sequence number. See also rte_reorder_insert() */
/* second cache line - fields only used in slow path or on TX */
MARKER cacheline1 __rte_cache_aligned;
--
1.9.3
next prev parent reply other threads:[~2015-02-20 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 12:10 [dpdk-dev] [PATCH 0/3] Misc fixes Sergio Gonzalez Monroy
2015-02-20 12:10 ` [dpdk-dev] [PATCH 1/3] doc: add librte_reorder to doxygen conf Sergio Gonzalez Monroy
2015-02-20 12:10 ` Sergio Gonzalez Monroy [this message]
2015-02-20 12:10 ` [dpdk-dev] [PATCH 3/3] examples/packet_ordering: move creation of reorder buffer Sergio Gonzalez Monroy
2015-02-24 2:04 ` [dpdk-dev] [PATCH 0/3] Misc fixes Thomas Monjalon
2015-02-24 8:46 ` Olivier MATZ
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=1424434253-6808-3-git-send-email-sergio.gonzalez.monroy@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.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).