From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, akhil.goyal@nxp.com
Cc: stable@dpdk.org, Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] [PATCH v2] bbdev: doxygen fix
Date: Sun, 19 Apr 2020 16:39:47 -0700 [thread overview]
Message-ID: <1587339588-243777-1-git-send-email-nicolas.chautru@intel.com> (raw)
v2: Fixes reference added in commit message (this was there from the beginning) though this is not critical for LTS branch.
Cosmetic changes for doxygen markup which were incorrect as raised during parallel code review.
Nicolas Chautru (1):
bbdev: doxygen update only
lib/librte_bbdev/rte_bbdev.h | 16 ++++++++--------
lib/librte_bbdev/rte_bbdev_op.h | 16 ++++++++--------
lib/librte_bbdev/rte_bbdev_pmd.h | 14 +++++++-------
3 files changed, 23 insertions(+), 23 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-04-19 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 23:39 Nicolas Chautru [this message]
2020-04-19 23:39 ` [dpdk-dev] [PATCH v2] bbdev: doxygen update only Nicolas Chautru
2020-05-09 21:37 ` Akhil Goyal
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=1587339588-243777-1-git-send-email-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=stable@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).