DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Kai Ji <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "adamx.dybkowski@intel.com" <adamx.dybkowski@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: Re: [dpdk-dev] [EXT] [dpdk-dev v2] test/crypto: copy offset data to oop dst buffer
Date: Wed, 5 May 2021 15:23:29 +0000	[thread overview]
Message-ID: <MW2PR18MB22841652144D1A8C7F12A463D8599@MW2PR18MB2284.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210505144513.9851-1-kai.ji@intel.com>

> Copy over the offset data required for auth in out-of-place op
> when auth offset and cipher offset are not aligned.
> 
> Fixes: e847fc512817 ("test/crypto: add encrypted digest case for AES-CTR-
> CMAC")
> Cc: adamx.dybkowski@intel.com
> 
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
> v2:
>    - rebase to head of for-main branch
> 
Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2021-05-05 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 23:26 [dpdk-dev] " Kai Ji
2021-05-05 14:45 ` [dpdk-dev] [dpdk-dev v2] " Kai Ji
2021-05-05 15:23   ` Akhil Goyal [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=MW2PR18MB22841652144D1A8C7F12A463D8599@MW2PR18MB2284.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=adamx.dybkowski@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=roy.fan.zhang@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).