dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Akhil Goyal <akhil.goyal@nxp.com>
Cc: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] cryptodev: make xform key pointer constant
Date: Thu, 20 Jun 2019 09:47:55 +0300	[thread overview]
Message-ID: <2169547.Q1UxdJ0fUF@xps> (raw)
In-Reply-To: <VE1PR04MB66393F728AD64EBBEB60CDE9E6E50@VE1PR04MB6639.eurprd04.prod.outlook.com>

19/06/2019 18:08, Akhil Goyal:
> Hi Fan,
> > >
> > > Hi Akhil,
> > >
> > > This patch was sent in 19.05 but I just found it can be applied to 19.08 RC0
> > > cleanly.
> > > Do you think I need to send a v4 (with no change) for 19.08?
> > >
> > No need to send a v4, I will take v3. Planning to take some patches next week.
> > Will let you know in case of some issue.
> 
> Please send a patch to update the release note and remove the deprecation notice
> Applied to dpdk-next-crypto

Please merge release notes updates in the same patch as code change.




  reply	other threads:[~2019-06-20  6:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 13:43 [PATCH] cryptodev: make xform key pointer constant Fan Zhang
2019-03-15 16:37 ` Kusztal, ArkadiuszX
2019-03-19  9:43 ` [PATCH v2] " Fan Zhang
2019-03-20 13:32   ` [PATCH v3] " Fan Zhang
2019-03-20 17:28     ` Kusztal, ArkadiuszX
2019-03-29 14:07     ` Akhil Goyal
2019-03-29 14:19       ` Thomas Monjalon
2019-03-29 15:48         ` Akhil Goyal
2019-03-29 16:01           ` Akhil Goyal
2019-05-28  9:52             ` [dpdk-dev] " Zhang, Roy Fan
2019-05-29  6:29               ` Akhil Goyal
2019-06-19 15:08                 ` Akhil Goyal
2019-06-20  6:47                   ` Thomas Monjalon [this message]
2019-06-24 13:35     ` [dpdk-dev] [PATCH v4] " Fan Zhang
2019-06-25 12:46       ` Akhil Goyal
2019-07-05 12:30         ` 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=2169547.Q1UxdJ0fUF@xps \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).