From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Yang, Zhiyong" <zhiyong.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"stable@dpdk.org" <stable@dpdk.org>,
"Doherty, Declan" <declan.doherty@intel.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Yang, Zhiyong" <zhiyong.yang@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] lib: fix wrong cast
Date: Tue, 23 Jan 2018 15:31:12 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC77EDC@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180123094813.65813-1-zhiyong.yang@intel.com>
> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Zhiyong Yang
> Sent: Tuesday, January 23, 2018 9:48 AM
> To: dev@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; thomas@monjalon.net;
> stable@dpdk.org; Doherty, Declan <declan.doherty@intel.com>;
> akhil.goyal@nxp.com; Yang, Zhiyong <zhiyong.yang@intel.com>
> Subject: [dpdk-stable] [PATCH] lib: fix wrong cast
>
> The wrong casts don't cause actual error, but they should conform to C
> standard.
>
> Fixes: c261d1431bd8 ("security: introduce security API and framework")
> Fixes: b3bbd9e5f265 ("cryptodev: support device independent sessions")
> Cc: stable@dpdk.org
> Cc: declan.doherty@intel.com
> Cc: akhil.goyal@nxp.com
>
> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2018-01-23 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 9:48 [dpdk-dev] " Zhiyong Yang
2018-01-23 9:59 ` Akhil Goyal
2018-01-23 15:31 ` De Lara Guarch, Pablo [this message]
2018-01-23 15:39 ` [dpdk-dev] [dpdk-stable] " 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=E115CCD9D858EF4F90C690B0DCB4D8976CC77EDC@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zhiyong.yang@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).