From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Ashish Gupta <Ashish.Gupta@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"narayanaprasad.athreya@cavium.com"
<narayanaprasad.athreya@cavium.com>,
"nidadavolu.murthy@cavium.com" <nidadavolu.murthy@cavium.com>,
Sunila Sahu <sunila.sahu@caviumnetworks.com>,
Shally Verma <shally.verma@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/1] crypto/openssl: replace macros by static inline functions
Date: Wed, 1 Aug 2018 16:17:32 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F908DE0@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <20180731141625.20225-2-Ashish.Gupta@caviumnetworks.com>
Hi Ashish,
> -----Original Message-----
> From: Ashish Gupta [mailto:Ashish.Gupta@caviumnetworks.com]
> Sent: Tuesday, July 31, 2018 3:16 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: dev@dpdk.org; narayanaprasad.athreya@cavium.com;
> nidadavolu.murthy@cavium.com; Sunila Sahu
> <sunila.sahu@caviumnetworks.com>; Shally Verma
> <shally.verma@caviumnetworks.com>; Ashish Gupta
> <ashish.gupta@caviumnetworks.com>
> Subject: [PATCH v1 1/1] crypto/openssl: replace macros by static inline functions
>
> Replace macros by static inline functions in openssl version compatibility layer
>
> Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com>
> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com>
> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
Thanks for the patch. Since this is not a fix, I will leave it for an early merge at start of the 18.11 cycle.
Pablo
next prev parent reply other threads:[~2018-08-01 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 14:16 [dpdk-dev] [PATCH v1 0/1] crypto/openssl: replace macros by inline routines Ashish Gupta
2018-07-31 14:16 ` [dpdk-dev] [PATCH v1 1/1] crypto/openssl: replace macros by static inline functions Ashish Gupta
2018-08-01 16:17 ` De Lara Guarch, Pablo [this message]
2018-08-23 13:48 ` Akhil Goyal
2018-08-23 13:57 ` 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=E115CCD9D858EF4F90C690B0DCB4D8977F908DE0@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=Ashish.Gupta@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=narayanaprasad.athreya@cavium.com \
--cc=nidadavolu.murthy@cavium.com \
--cc=shally.verma@caviumnetworks.com \
--cc=sunila.sahu@caviumnetworks.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).