From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ip_pipeline: fix build error for 32 bit gcc target
Date: Fri, 8 Apr 2016 19:37:10 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025108F1@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1460135607-147140-1-git-send-email-jasvinder.singh@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jasvinder Singh
> Sent: Friday, April 8, 2016 6:13 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] ip_pipeline: fix build error for 32 bit gcc
> target
>
> error log:
> ip_pipeline/pipeline/pipeline_routing_be.c:1537: integer constant is too
> large for 'long' type compilation terminated due to -Wfatal-errors
>
> Fixes: 0ae7275810f1 ("examples/ip_pipeline: add more functions to routing
> pipeline")
>
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
prev parent reply other threads:[~2016-04-08 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 17:13 Jasvinder Singh
2016-04-08 17:53 ` De Lara Guarch, Pablo
2016-04-08 20:17 ` Thomas Monjalon
2016-04-08 19:37 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2025108F1@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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).