DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: add default linux configuration
Date: Tue, 16 Feb 2016 12:23:12 +0100	[thread overview]
Message-ID: <2202345.QkgQ4lTT1r@xps13> (raw)
In-Reply-To: <20160216111635.GA930@sivlogin002.ir.intel.com>

2016-02-16 11:16, Ferruh Yigit:
> On Thu, Jan 28, 2016 at 02:31:45PM +0000, Bernard Iremonger wrote:
> > add config/defconfig_x86_64-default-linuxapp-gcc file.
> > 
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> 
> Apart from configuration related discussion,
> this patch was helpful for me to notice "default" machine type, and difference between "native",
> so I believe it is good to have this as sample config.

The justification is strange. We are not going to have a config file
for every combinations.
Defaulting defconfig files to the native machine natural to me.

> Also not scope of this patch but I agree on Bruce's comment on renaming "default" machine type to "generic",
> I can send a patch for this if there is a demand.

default is an Intel core 2. Why generic is a better name?

  reply	other threads:[~2016-02-16 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 14:31 Bernard Iremonger
2016-02-12 12:31 ` Panu Matilainen
2016-02-12 15:04   ` Thomas Monjalon
2016-02-12 16:59     ` Ferruh Yigit
2016-02-12 17:13       ` Thomas Monjalon
2016-02-12 17:23         ` Ferruh Yigit
2016-02-16 11:16 ` Ferruh Yigit
2016-02-16 11:23   ` Thomas Monjalon [this message]
2016-02-16 12:08     ` Ferruh Yigit
2016-02-17 10:42       ` Iremonger, Bernard

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=2202345.QkgQ4lTT1r@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).