patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 2/2] doc: fixes the limitations	for dpaa2 sec
Date: Thu, 5 Jul 2018 08:16:31 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8E5251@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <35436c8e-a04b-258d-9052-772fb5d5a0e9@nxp.com>



> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Akhil Goyal
> Sent: Thursday, June 21, 2018 3:22 PM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 2/2] doc: fixes the limitations for
> dpaa2 sec
> 
> 
> 
> On 6/21/2018 2:43 PM, Hemant Agrawal wrote:
> > Fixes: 37f96eb01bce ("crypto/dpaa2_sec: support scatter gather")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

Applied to dpdk-next-crypto.
Thanks,

Pablo


  reply	other threads:[~2018-07-05  8:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21  9:13 [dpdk-stable] [PATCH 1/2] doc: fixes the limitations for dpaa sec Hemant Agrawal
2018-06-21  9:13 ` [dpdk-stable] [PATCH 2/2] doc: fixes the limitations for dpaa2 sec Hemant Agrawal
2018-06-21 14:22   ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
2018-07-05  8:16     ` De Lara Guarch, Pablo [this message]
2018-06-21 14:22 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] doc: fixes the limitations for dpaa sec Akhil Goyal
2018-07-05  8:16   ` De Lara Guarch, Pablo

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=E115CCD9D858EF4F90C690B0DCB4D8977F8E5251@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).