From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] config: factorize configurations
Date: Wed, 21 May 2014 16:33:46 +0200 [thread overview]
Message-ID: <9864870.5rZgTyaARp@xps13> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA19BC8@IRSMSX103.ger.corp.intel.com>
2014-05-14 15:10, Richardson, Bruce:
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Marchand
> > Sent: Wednesday, May 14, 2014 3:58 PM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] [PATCH 1/3] config: factorize configurations
> >
> > linux and bsd default configurations now have their own default common
> > configuration files.
> > Specific options are then set in the specific files.
> > This makes it easier to globally enable/disable some features in DPDK for
> > multiple targets.
> >
>
> Good idea. Perhaps the bsdapp and linuxapp common files could be even merged
> themselves in future. Otherwise ...
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied for version 1.7.0.
Thanks
--
Thomas
next prev parent reply other threads:[~2014-05-21 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 14:58 [dpdk-dev] [PATCH 0/3] configs cleanup David Marchand
2014-05-14 14:58 ` [dpdk-dev] [PATCH 1/3] config: factorize configurations David Marchand
2014-05-14 15:10 ` Richardson, Bruce
2014-05-19 8:13 ` David Marchand
2014-05-21 14:33 ` Thomas Monjalon [this message]
2014-05-14 14:58 ` [dpdk-dev] [PATCH 2/3] config: rename "default" configuration file as "native" David Marchand
2014-05-14 15:12 ` Richardson, Bruce
2014-05-21 14:35 ` Thomas Monjalon
2014-05-14 14:58 ` [dpdk-dev] [PATCH 3/3] config: rename "default" machine type as "core2" David Marchand
2014-05-14 15:18 ` Richardson, Bruce
2014-05-19 8:20 ` David Marchand
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=9864870.5rZgTyaARp@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
/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).