From: Akhil Goyal <akhil.goyal@nxp.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Cc: "Doherty, Declan" <declan.doherty@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Gaetan Rivet <gaetan.rivet@6wind.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 1/3] security: fix device operation type
Date: Mon, 8 Jan 2018 15:35:47 +0530 [thread overview]
Message-ID: <a967c330-ec09-f0c1-2c54-a6cda045841b@nxp.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8976CC69611@IRSMSX108.ger.corp.intel.com>
On 1/8/2018 3:28 PM, De Lara Guarch, Pablo wrote:
>
>
>> -----Original Message-----
>> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Nelio
>> Laranjeiro
>> Sent: Friday, November 24, 2017 12:07 PM
>> To: Akhil Goyal <akhil.goyal@nxp.com>
>> Cc: Doherty, Declan <declan.doherty@intel.com>; dev@dpdk.org; Gaetan
>> Rivet <gaetan.rivet@6wind.com>; stable@dpdk.org
>> Subject: Re: [dpdk-stable] [PATCH v2 1/3] security: fix device operation type
>>
>> On Fri, Nov 24, 2017 at 03:03:52PM +0530, Akhil Goyal wrote:
>>> Hi Nelio,
>>> On 11/23/2017 3:32 PM, Nelio Laranjeiro wrote:
>>>> Device operation pointers should be constant to avoid any
>>>> modification while it is in use.
>>>>
>>>> Fixes: c261d1431bd8 ("security: introduce security API and
>>>> framework")
>>>> Cc: akhil.goyal@nxp.com
>>>> Cc: stable@dpdk.org
>>>>
>>>> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
> Akhil, do you agree with the change? I am waiting for an ack here to integrate this patch with the rest of the patchset.
>
> Thanks,
> Pablo
>
>
Yes I agree to this change.
Just suggesting this change for crypto ops as well.
Acked-by: Akhil Goyal <akhil.goyal@nxp.com
next prev parent reply other threads:[~2018-01-08 10:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 8:10 [dpdk-stable] [PATCH " Nelio Laranjeiro
2017-11-22 8:10 ` [dpdk-stable] [PATCH 2/3] crypto: fix pedentic compilation errors Nelio Laranjeiro
2017-11-22 9:48 ` De Lara Guarch, Pablo
2017-11-22 10:35 ` Nelio Laranjeiro
2017-11-22 13:56 ` [dpdk-stable] [dpdk-dev] " Neil Horman
2017-11-22 14:31 ` Gaëtan Rivet
2017-11-22 16:50 ` De Lara Guarch, Pablo
2017-11-22 8:10 ` [dpdk-stable] [PATCH 3/3] security: fix pedentic compilation Nelio Laranjeiro
2017-11-23 10:02 ` [dpdk-stable] [PATCH v2 1/3] security: fix device operation type Nelio Laranjeiro
2017-11-24 9:33 ` Akhil Goyal
2017-11-24 12:07 ` Nelio Laranjeiro
2018-01-08 9:58 ` De Lara Guarch, Pablo
2018-01-08 10:05 ` Akhil Goyal [this message]
2018-01-08 12:34 ` De Lara Guarch, Pablo
2017-11-23 10:02 ` [dpdk-stable] [PATCH v2 2/3] crypto: fix pedantic compilation errors Nelio Laranjeiro
2017-12-11 11:49 ` De Lara Guarch, Pablo
2017-12-11 12:42 ` Nelio Laranjeiro
2017-12-11 13:54 ` De Lara Guarch, Pablo
2017-12-11 14:16 ` Nelio Laranjeiro
2018-01-08 10:00 ` [dpdk-stable] [dpdk-dev] " De Lara Guarch, Pablo
2018-01-08 12:35 ` [dpdk-stable] " De Lara Guarch, Pablo
2017-11-23 10:02 ` [dpdk-stable] [PATCH v2 3/3] security: fix pedantic compilation Nelio Laranjeiro
2017-11-24 9:34 ` Akhil Goyal
2018-01-08 12:35 ` De Lara Guarch, Pablo
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=a967c330-ec09-f0c1-2c54-a6cda045841b@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@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).