DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce driver name changes
Date: Wed, 27 Jul 2016 10:30:16 +0200	[thread overview]
Message-ID: <1531579.YlOdWedZ0T@xps13> (raw)
In-Reply-To: <20160722151336.GF9044@6wind.com>

2016-07-22 17:13, Adrien Mazarguil:
> > > >> From: De Lara Guarch, Pablo
> > > >>> Driver names for all the supported devices in DPDK do not have
> > > >>> a naming convention. Some are using a prefix, some are not
> > > >>> and some have long names. Driver names are used when creating
> > > >>> virtual devices, so it is useful to have consistency in the names.
> > > >>>
> > > >>> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> 
> So what about using "net/" instead of "net_" to share names with commit
> prefixes and folders?

+1 for net/ in names

Anyway,
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>

  reply	other threads:[~2016-07-27  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 16:56 Pablo de Lara
2016-07-11  5:08 ` Christian Ehrhardt
2016-07-22 12:37 ` De Lara Guarch, Pablo
2016-07-22 12:54   ` Adrien Mazarguil
2016-07-22 13:18     ` Ferruh Yigit
2016-07-22 14:15       ` De Lara Guarch, Pablo
2016-07-22 14:20         ` Thomas Monjalon
2016-07-22 15:13         ` Adrien Mazarguil
2016-07-27  8:30           ` Thomas Monjalon [this message]
2016-07-28 17:22 ` Maxime Coquelin
2016-07-28 17:47 ` Jerin Jacob
2016-07-28 17:54   ` 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=1531579.YlOdWedZ0T@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=pablo.de.lara.guarch@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).