From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] Change optimization flag for Intel QuickAssist Technology driver Makefile
Date: Tue, 7 Jun 2016 17:13:02 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C903393B936A@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1465318694-20727-1-git-send-email-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Tuesday, June 7, 2016 5:58 PM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; Griffin, John
> <john.griffin@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>;
> Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH 0/2] Change optimization flag for Intel QuickAssist
> Technology driver Makefile
>
> This patch changes to -O3 optimization flag in Intel QuickAssist Technology
> driver Makefile
>
> Arek Kusztal (2):
> qat: add aad_len variable to avoid GCC break strict-aliasing rules
> warning
> qat: change optimization flag for Intel QuickAssist Technology
> Makefile
>
> drivers/crypto/qat/Makefile | 1 +
> drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 8 +++++---
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> --
> 2.1.0
Series-Acked-by: Deepak Kumar JAIN <deepak.k.jain@intel.com
next prev parent reply other threads:[~2016-06-07 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 16:58 Arek Kusztal
2016-06-07 16:58 ` [dpdk-dev] [PATCH 1/2] qat: add aad_len variable to avoid GCC break strict-aliasing rules warning Arek Kusztal
2016-06-07 16:58 ` [dpdk-dev] [PATCH 2/2] qat: change optimization flag for Intel QuickAssist Technology Makefile Arek Kusztal
2016-06-07 17:13 ` Jain, Deepak K [this message]
2016-06-07 19:37 ` [dpdk-dev] [PATCH 0/2] Change optimization flag for Intel QuickAssist Technology driver Makefile 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=A09C9DDE180C7E429EC68E2BFB95C903393B936A@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).