From: Akhil Goyal <akhil.goyal@nxp.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature
Date: Wed, 12 Feb 2020 13:17:15 +0000 [thread overview]
Message-ID: <VE1PR04MB663934B5B20B57A5BC3DA99DE61B0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <BN6PR11MB1796C505785D6BC99B07F0C3E4190@BN6PR11MB1796.namprd11.prod.outlook.com>
> >
> > This commit fixes missing release notes for dual thread feature.
> >
> > Fixes: 026f21c0b951 ("common/qat: support dual threads for
> enqueue/dequeue")
> >
> > Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Applied to dpdk-next-crypto
Squashed with http://patches.dpdk.org/patch/65413/
As both are adding release notes for related features.
prev parent reply other threads:[~2020-02-12 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 7:28 Arek Kusztal
2020-01-31 7:28 ` [dpdk-dev] [PATCH] crypto/qat: fix not included release note for coalescing feature Arek Kusztal
2020-02-10 10:17 ` Trahe, Fiona
2020-02-10 10:15 ` [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature Trahe, Fiona
2020-02-12 13:17 ` 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=VE1PR04MB663934B5B20B57A5BC3DA99DE61B0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).