patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Grandi, Andrea" <andrea.grandi@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 1/2] doc: fix lists of supported algorithms
Date: Mon, 11 Dec 2017 10:22:46 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC58F6E@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20171122180312.19014-1-andrea.grandi@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Andrea Grandi
> Sent: Wednesday, November 22, 2017 6:03 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/2] doc: fix lists of supported algorithms
> 
> Add a missing space must before the first item of the list to display it
> correctly in the User Guide.
> 
> Fixes: d61f70b4c918 ("crypto/libcrypto: add driver for OpenSSL library")
> Fixes: b79e4c00af0e ("cryptodev: use AES-GCM/CCM as AEAD algorithms")
> 
> Signed-off-by: Andrea Grandi <andrea.grandi@intel.com>

Series applied to dpdk-next-crypto.
Thanks,

Pablo

      parent reply	other threads:[~2017-12-11 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 18:03 [dpdk-stable] " Andrea Grandi
2017-11-22 18:03 ` [dpdk-stable] [PATCH 2/2] doc: fix format in OpenSSL installation guide Andrea Grandi
2017-12-11 10:04   ` [dpdk-stable] [dpdk-dev] " De Lara Guarch, Pablo
2017-12-11 10:03 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] doc: fix lists of supported algorithms De Lara Guarch, Pablo
2017-12-11 10:22 ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D8976CC58F6E@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=andrea.grandi@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).