From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: fix not included release note for coalescing feature
Date: Mon, 10 Feb 2020 10:17:49 +0000 [thread overview]
Message-ID: <BN6PR11MB1796E828C64453273E448107E4190@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200131072848.6748-2-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Friday, January 31, 2020 7:29 AM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] crypto/qat: fix not included release note for coalescing feature
>
> This patch fixes not included in original patch release note
>
> Fixes: 6cde900bd59d ("common/qat: remove tail write coalescing")
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2020-02-10 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 7:28 [dpdk-dev] [PATCH] crypto/qat: fix missing release note for dual thread feature 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 [this message]
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
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=BN6PR11MB1796E828C64453273E448107E4190@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.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).