From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 2/3] examples/l3fwd: fix build without SSE4.1
Date: Mon, 8 Feb 2016 14:09:32 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8A1616@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1454525799-25552-3-git-send-email-thomas.monjalon@6wind.com>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, February 03, 2016 6:57 PM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin; Wang, Zhihong; De Lara Guarch, Pablo; Dumitrescu,
> Cristian
> Subject: [PATCH 2/3] examples/l3fwd: fix build without SSE4.1
>
> clang reports this error:
> examples/l3fwd/main.c:550:1: error: unused function 'send_packetsx4'
>
> The function is used only when ENABLE_MULTI_BUFFER_OPTIMIZE is 1.
>
> Fixes: 96ff445371e0 ("examples/l3fwd: reorganise and optimize LPM code
> path")
> Fixes: 6f1c1e28d98e ("examples/l3fwd: fix build with exact-match enabled")
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2016-02-08 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 18:56 [PATCH 0/3] fix build for default machine Thomas Monjalon
2016-02-03 18:56 ` [PATCH 1/3] eal/x86: fix build with clang for old AVX Thomas Monjalon
2016-02-04 3:35 ` Wang, Zhihong
2016-02-04 8:47 ` Thomas Monjalon
2016-02-04 9:21 ` Thomas Monjalon
2016-02-03 18:56 ` [PATCH 2/3] examples/l3fwd: fix build without SSE4.1 Thomas Monjalon
2016-02-08 14:09 ` De Lara Guarch, Pablo [this message]
2016-02-03 18:56 ` [PATCH 3/3] examples/ip_pipeline: fix build for x86_64 without SSE4.2 Thomas Monjalon
2016-02-16 6:53 ` [PATCH 0/3] fix build for default machine 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=E115CCD9D858EF4F90C690B0DCB4D8973C8A1616@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.