DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sean Morrissey <sean.morrissey@intel.com>
Cc: dev@dpdk.org, Sean Morrissey <sean.morrissey@intel.com>, stable@dpdk.org
Subject: [PATCH v2] doc: fix telemetry example for cryptodev
Date: Wed,  9 Mar 2022 09:33:10 +0000	[thread overview]
Message-ID: <20220309093310.2855587-1-sean.morrissey@intel.com> (raw)
In-Reply-To: <20220308155656.2254466-1-sean.morrissey@intel.com>

Blank line added to the final telemetry example for the
cryptography device library as to fix the example
rendering.

Fixes: 1c559ee8469 ("cryptodev: add telemetry endpoint for capabilities")
Cc: stable@dpdk.org

Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
---
 doc/guides/prog_guide/cryptodev_lib.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/guides/prog_guide/cryptodev_lib.rst b/doc/guides/prog_guide/cryptodev_lib.rst
index ba4c592b84..edd11059bc 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -1211,6 +1211,7 @@ are shown below.
      "enqueue_err_count": 0, "dequeue_err_count": 0}}
 
 #. Get the capabilities of a particular Crypto device::
+
      --> /cryptodev/caps,0
      {"/cryptodev/caps": {"crypto_caps": [<array of serialized bytes of
      capabilities>], "crypto_caps_n": <number of capabilities>}}
-- 
2.25.1


  parent reply	other threads:[~2022-03-09  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 15:56 [PATCH v1] " Sean Morrissey
2022-03-08 22:36 ` Thomas Monjalon
2022-03-09  9:33 ` Sean Morrissey [this message]
2022-03-09 15:11   ` [PATCH v2] " Power, Ciara
2022-03-16 19:26     ` 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=20220309093310.2855587-1-sean.morrissey@intel.com \
    --to=sean.morrissey@intel.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).