From: Nicolas Chautru <nicolas.chautru@intel.com>
To: dev@dpdk.org, gakhil@marvell.com
Cc: Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [PATCH v2 0/1] doc: update to include bbdev snippet using literalinclude
Date: Wed, 12 Oct 2022 11:16:21 -0700 [thread overview]
Message-ID: <20221012181622.8068-1-nicolas.chautru@intel.com> (raw)
v2: Rebased to latest to avoid git am failure when applying.
v1: Update to include bbdev snippet using literalinclude.
Nicolas Chautru (1):
doc: update to include bbdev snippet using literalinclude
doc/guides/prog_guide/bbdev.rst | 105 +++++++-------------------------
lib/bbdev/rte_bbdev_op.h | 15 +++++
2 files changed, 38 insertions(+), 82 deletions(-)
--
2.37.1
next reply other threads:[~2022-10-12 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:16 Nicolas Chautru [this message]
2022-10-12 18:16 ` [PATCH v2 1/1] " Nicolas Chautru
2022-10-27 14:23 ` [EXT] " 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=20221012181622.8068-1-nicolas.chautru@intel.com \
--to=nicolas.chautru@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).