From: Thomas Monjalon <thomas@monjalon.net>
To: Sean Morrissey <sean.morrissey@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] doc: fix telemetry example for cryptodev
Date: Tue, 08 Mar 2022 23:36:52 +0100 [thread overview]
Message-ID: <5869074.FjKLVJYuhi@thomas> (raw)
In-Reply-To: <20220308155656.2254466-1-sean.morrissey@intel.com>
08/03/2022 16:56, Sean Morrissey:
> Blank line added to the final telemetry example for the
> cryptography device library as to fix the example
> rendering.
Even for a simple fix like that, you need to add a Fixes: line
so we know where to backport (or not).
>
> Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> ---
> #. Get the capabilities of a particular Crypto device::
> +
> --> /cryptodev/caps,0
next prev parent reply other threads:[~2022-03-08 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 15:56 Sean Morrissey
2022-03-08 22:36 ` Thomas Monjalon [this message]
2022-03-09 9:33 ` [PATCH v2] " Sean Morrissey
2022-03-09 15:11 ` 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=5869074.FjKLVJYuhi@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=sean.morrissey@intel.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).