From: Kevin Traynor <ktraynor@redhat.com>
To: Sean Morrissey <sean.morrissey@intel.com>
Cc: Ciara Power <ciara.power@intel.com>, dpdk stable <stable@dpdk.org>
Subject: patch 'doc: fix telemetry example in cryptodev guide' has been queued to stable release 21.11.1
Date: Mon, 21 Mar 2022 14:43:39 +0000 [thread overview]
Message-ID: <20220321144340.64983-3-ktraynor@redhat.com> (raw)
In-Reply-To: <20220321144340.64983-1-ktraynor@redhat.com>
Hi,
FYI, your patch has been queued to stable release 21.11.1
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 03/22/22. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/kevintraynor/dpdk-stable
This queued commit can be viewed at:
https://github.com/kevintraynor/dpdk-stable/commit/4586b6b8c23cb6c54844001f5bb61204a181934f
Thanks.
Kevin
---
From 4586b6b8c23cb6c54844001f5bb61204a181934f Mon Sep 17 00:00:00 2001
From: Sean Morrissey <sean.morrissey@intel.com>
Date: Wed, 9 Mar 2022 09:33:10 +0000
Subject: [PATCH] doc: fix telemetry example in cryptodev guide
[ upstream commit 4ac7359b5c05f7712f8f85c2633e11388e68edd8 ]
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")
Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
Acked-by: Ciara Power <ciara.power@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 8766bc34a9..8e403cb949 100644
--- a/doc/guides/prog_guide/cryptodev_lib.rst
+++ b/doc/guides/prog_guide/cryptodev_lib.rst
@@ -1310,4 +1310,5 @@ are shown below.
#. Get the capabilities of a particular Crypto device::
+
--> /cryptodev/caps,0
{"/cryptodev/caps": {"crypto_caps": [<array of serialized bytes of
--
2.34.1
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2022-03-21 14:24:08.484174308 +0000
+++ 0003-doc-fix-telemetry-example-in-cryptodev-guide.patch 2022-03-21 14:24:08.414777664 +0000
@@ -1 +1 @@
-From 4ac7359b5c05f7712f8f85c2633e11388e68edd8 Mon Sep 17 00:00:00 2001
+From 4586b6b8c23cb6c54844001f5bb61204a181934f Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 4ac7359b5c05f7712f8f85c2633e11388e68edd8 ]
+
@@ -11 +12,0 @@
-Cc: stable@dpdk.org
@@ -20 +21 @@
-index ba4c592b84..edd11059bc 100644
+index 8766bc34a9..8e403cb949 100644
@@ -23 +24 @@
-@@ -1212,4 +1212,5 @@ are shown below.
+@@ -1310,4 +1310,5 @@ are shown below.
next prev parent reply other threads:[~2022-03-21 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:43 patch 'doc: replace characters for (R) symbol in Linux " Kevin Traynor
2022-03-21 14:43 ` patch 'doc: fix missing note on UIO module " Kevin Traynor
2022-03-21 14:43 ` Kevin Traynor [this message]
2022-03-21 14:43 ` patch 'raw/ifpga: fix build with optimization' " Kevin Traynor
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=20220321144340.64983-3-ktraynor@redhat.com \
--to=ktraynor@redhat.com \
--cc=ciara.power@intel.com \
--cc=sean.morrissey@intel.com \
--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).