DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] have net drivers use a standard map file name format
Date: Thu, 14 Sep 2017 16:36:49 +0000	[thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0721D65F4@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <fb2d085a-c9a1-13f8-e285-2ae87d7c7a75@intel.com>



> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Thursday, September 14, 2017 5:34 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; Tan, Jianfeng
> <jianfeng.tan@intel.com>; Doherty, Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [PATCH 0/2] have net drivers use a standard map file name
> format
> 
> On 9/14/2017 4:57 PM, Bruce Richardson wrote:
> > rename some of the version.map files that don't match the standard
> > naming convention. For future meson build system, this will save us
> > having to specify for each driver what the filename of its map file is.
> >
> > Bruce Richardson (2):
> >   net/bonding: rename map file to standard name
> >   net/xenvirt: rename map file to standard name
> 
> +1 for bonding,
> but xenvirt is going away in this release, can we drop that one?
> 
Good point. Please ignore patch 2, and take only patch 1.

      reply	other threads:[~2017-09-14 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 15:57 Bruce Richardson
2017-09-14 15:57 ` [dpdk-dev] [PATCH 1/2] net/bonding: rename map file to standard name Bruce Richardson
2017-09-20 13:42   ` Ferruh Yigit
2017-09-14 15:57 ` [dpdk-dev] [PATCH 2/2] net/xenvirt: " Bruce Richardson
2017-09-20 13:42   ` Ferruh Yigit
2017-09-14 16:34 ` [dpdk-dev] [PATCH 0/2] have net drivers use a standard map file name format Ferruh Yigit
2017-09-14 16:36   ` Richardson, Bruce [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=59AF69C657FD0841A61C55336867B5B0721D65F4@IRSMSX103.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianfeng.tan@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).