DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
	Declan Doherty <declan.doherty@intel.com>,
	Fan Zhang <roy.fan.zhang@intel.com>,
	Ashish Gupta <ashishg@marvell.com>, Ray Kinsella <mdr@ashroe.eu>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH RFC 0/3] Add UADK compression and crypto PMD
Date: Fri, 20 May 2022 13:48:11 +0000	[thread overview]
Message-ID: <CO6PR18MB448416D6DFEF85F39097CCE8D8D39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1e078d4d-d31c-a926-aa15-56e312876a42@linaro.org>

Hi Zhangfei,
> Hi, Akhil
> 
> On 2022/5/20 下午7:49, Akhil Goyal wrote:
> >> Supported hardware platforms:
> >> HiSilicon Kunpeng920 and Kunpeng930
> >>
> >> The PMD relies on UADK Interface:
> > I hope this set is for DPDK 22.11
> Oh, should be based on v22.03?
> 
> The patchset is based on 45f04d8 version: 21.11.0
> 
> Just tried on v22.03, the last patch can not be applied by git am, but
> can be done patch cmd.
> 
> Will update on v22.03 next time.

The patches should be rebased over the current TOT of
http://git.dpdk.org/next/dpdk-next-crypto/log/ whenever you send
a new version.
The question that I asked is ..
What is the target release for which this patchset is intended to?
Current release cycle is DPDK-22.07 for which this patchset is late.
As we had the V1 deadline last month.
This patchset can go for next release cycle which is 22.11.

You can check the general contributing guidelines here:
https://doc.dpdk.org/guides/contributing/patches.html

Regards,
Akhil

  reply	other threads:[~2022-05-20 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 11:31 Zhangfei Gao
2022-05-20 11:31 ` [PATCH RFC 1/3] compress: add UADK compression PMD Zhangfei Gao
2022-05-20 11:31 ` [PATCH RFC 2/3] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-05-20 11:49 ` [EXT] [PATCH RFC 0/3] Add UADK compression and crypto PMD Akhil Goyal
2022-05-20 13:21   ` Zhangfei Gao
2022-05-20 13:48     ` Akhil Goyal [this message]
2022-05-23  1:35       ` Zhangfei Gao

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=CO6PR18MB448416D6DFEF85F39097CCE8D8D39@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ashishg@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --cc=roy.fan.zhang@intel.com \
    --cc=zhangfei.gao@linaro.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).