patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-stable] [PATCH v2] crypto/dpaa2_sec: remove iova conversion for fle address
Date: Wed, 9 May 2018 14:35:49 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CD055C2@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180509124324.22258-1-shreyansh.jain@nxp.com>



> -----Original Message-----
> From: Shreyansh Jain [mailto:shreyansh.jain@nxp.com]
> Sent: Wednesday, May 9, 2018 1:43 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; akhil.goyal@nxp.com; stable@dpdk.org;
> hemant.agrawal@nxp.com
> Subject: [PATCH v2] crypto/dpaa2_sec: remove iova conversion for fle address
> 
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> 
> fle is already in virtual addressing mode - no need to perform address conversion
> for it.
> 
> Fixes: 8d1f3a5d751b ("crypto/dpaa2_sec: support crypto operation")
> Cc: akhil.goyal@nxp.com
> 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-05-09 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180509092642.9092-1-shreyansh.jain@nxp.com>
     [not found] ` <ca1fb35f-cdae-58b0-f566-aac579509377@nxp.com>
2018-05-09 10:24   ` [dpdk-stable] [dpdk-dev] [PATCH] " De Lara Guarch, Pablo
2018-05-09 12:43 ` [dpdk-stable] [PATCH v2] " Shreyansh Jain
2018-05-09 14:35   ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CD055C2@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=shreyansh.jain@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).