DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] cryptodev: fix C11 extensions in exported header
Date: Fri, 4 Aug 2017 12:41:40 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBE8DC9@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <61d6d83aca3273eb3ed0b6b204cf0c6fb131d635.1501847638.git.adrien.mazarguil@6wind.com>



> -----Original Message-----
> From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com]
> Sent: Friday, August 4, 2017 12:56 PM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH 2/2] cryptodev: fix C11 extensions in exported header
> 
> Fix issues reported by check-includes.sh:
> 
>  rte_crypto_sym.h:586:3: error: anonymous structs are a C11 extension
>      [-Werror,-Wc11-extensions]
>  rte_crypto_sym.h:510:2: error: anonymous unions are a C11 extension
>      [-Werror,-Wc11-extensions]
> 
> Fixes: b59502a5e3d0 ("cryptodev: add AEAD parameters in crypto
> operation")
> Cc: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> 
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Patch looks good, although check-git-log.sh complains about it:

Wrong tag:
        Fix issues reported by check-includes.sh:

Apart from this.

Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

  reply	other threads:[~2017-08-04 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 11:56 [dpdk-dev] [PATCH 1/2] ethdev: " Adrien Mazarguil
2017-08-04 11:56 ` [dpdk-dev] [PATCH 2/2] cryptodev: " Adrien Mazarguil
2017-08-04 12:41   ` De Lara Guarch, Pablo [this message]
2017-08-04 13:37 ` [dpdk-dev] [PATCH 1/2] ethdev: " Dumitrescu, Cristian
2017-08-04 23:16   ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBE8DC9@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).