From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Gajdzica, MaciejX T" <maciejx.t.gajdzica@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6 00/11] ip_pipeline: ip_pipeline application enhancements
Date: Tue, 7 Jul 2015 11:33:49 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912632397179@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <95755673.A8d1Dkkkpx@xps13>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, July 7, 2015 9:28 AM
> To: Gajdzica, MaciejX T
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v6 00/11] ip_pipeline: ip_pipeline application
> enhancements
>
> 2015-07-07 10:09, Maciej Gajdzica:
> > Changes in v4:
> > - fixed build issue with gcc 5
> > - fixed bugs in flow classification and firewall pipelines
> >
> > Changes in v5:
> > - fixed build issue with clang 3.6
> >
> > Changes in v6:
> > - fixed build issues with icc 15
> > - fixed build issues with gcc 32bit
>
> Please, from now, avoid sending patches without having checked build with
> GCC 5 32/64-bit, clang and ICC if possible.
> Thanks
Will do, apologies for all these issues. Thanks, Thomas!
next prev parent reply other threads:[~2015-07-07 11:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 8:09 Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 01/11] ip_pipeline: add parsing for config files with new syntax Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 02/11] ip_pipeline: added config checks Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 03/11] ip_pipeline: modified init to match new params struct Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 04/11] ip_pipeline: moved pipelines to separate folder Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 05/11] ip_pipeline: added master pipeline Maciej Gajdzica
2015-07-08 22:33 ` Thomas Monjalon
2015-07-09 8:03 ` Gajdzica, MaciejX T
2015-07-09 9:58 ` Gajdzica, MaciejX T
2015-07-09 10:00 ` Dumitrescu, Cristian
2015-07-09 10:06 ` Gajdzica, MaciejX T
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 06/11] ip_pipeline: added application thread Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 07/11] ip_pipeline: moved config files to separate folder Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 08/11] ip_pipeline: added new implementation of passthrough pipeline Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 09/11] ip_pipeline: added new implementation of firewall pipeline Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 10/11] ip_pipeline: added new implementation of routing pipeline Maciej Gajdzica
2015-07-07 8:09 ` [dpdk-dev] [PATCH v6 11/11] ip_pipeline: added new implementation of flow classification pipeline Maciej Gajdzica
2015-07-07 8:27 ` [dpdk-dev] [PATCH v6 00/11] ip_pipeline: ip_pipeline application enhancements Thomas Monjalon
2015-07-07 11:33 ` Dumitrescu, Cristian [this message]
2015-07-07 9:23 ` Dumitrescu, Cristian
2015-07-09 15:27 ` 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=3EB4FA525960D640B5BDFFD6A3D8912632397179@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=maciejx.t.gajdzica@intel.com \
--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 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).