From: Akhil Goyal <akhil.goyal@nxp.com>
To: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] crypto/qat: support DOCSIS AES-256
Date: Mon, 11 May 2020 16:14:39 +0000 [thread overview]
Message-ID: <VI1PR04MB3168AE4FBCB54F27FC3438C0E6A10@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3725D48E69A5CABDB28FD2969CA10@MN2PR11MB3725.namprd11.prod.outlook.com>
In that case you should send only the incremental patch and add a Fixes reference to the original patch.
>
> These are the patches for QAT AES-256 DOCSIS along with the documentation
> update (which was missing from previous version)
>
> Regards,
> Mairtin
>
> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Monday, May 11, 2020 2:14 PM
> To: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH v3] crypto/qat: support DOCSIS AES-256
>
> I believe this patch is already applied. Why is it recent?
prev parent reply other threads:[~2020-05-11 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 9:04 [dpdk-dev] [PATCH v2 1/2] crypto/qat: support DOCSIS AES-256 Mairtin o Loingsigh
2020-02-26 9:04 ` [dpdk-dev] [PATCH v2 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-02-26 10:42 ` Trahe, Fiona
2020-02-26 10:41 ` [dpdk-dev] [PATCH v2 1/2] crypto/qat: support DOCSIS AES-256 Trahe, Fiona
2020-03-25 19:10 ` Akhil Goyal
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] " Mairtin o Loingsigh
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] test/crypto: add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-05-11 13:10 ` Akhil Goyal
2020-05-11 10:19 ` [dpdk-dev] [PATCH v3] doc: QAT support for AES-256 DOCSIS Mairtin o Loingsigh
2020-05-11 13:12 ` Akhil Goyal
2020-05-11 13:14 ` [dpdk-dev] [PATCH v3] crypto/qat: support DOCSIS AES-256 Akhil Goyal
2020-05-11 14:03 ` O'loingsigh, Mairtin
2020-05-11 16:14 ` 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=VI1PR04MB3168AE4FBCB54F27FC3438C0E6A10@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=mairtin.oloingsigh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.