DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, DPDK <dev@dpdk.org>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"Hemant Agrawal" <hemant.agrawal@nxp.com>,
	Gaetan Rivet <gaetan.rivet@6wind.com>,
	 Pascal Mazon <pascal.mazon@6wind.com>
Cc: "Zhu, Heqing" <heqing.zhu@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Vincent JARDIN <vincent.jardin@6wind.com>
Subject: Re: [dpdk-dev] Vendor specific sub-trees under next-net
Date: Sun, 15 Oct 2017 05:28:16 +0000	[thread overview]
Message-ID: <VI1PR05MB31493ABD23E0E9955B6755A9C34E0@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <15fd757d-d540-d787-f525-2c881502970a@intel.com>

Friday, October 13, 2017 2:31 AM, Ferruh Yigit:
> On 10/13/2017 12:29 AM, Ferruh Yigit wrote:
> > Hi Thomas, et al
> >
> > Previously it has been mentioned [1] to have vendor specific driver
> > trees under next-net.
> >
> > And recently Mellanox agreed to have a Mellanox tree [2].
> >
> > Intel also agrees to have next-net-intel, and Helin will be
> > maintaining it, thanks to Helin for volunteering.
> >
> > Other vendors with multiple drivers are Cavium, 6wind and NXP.
> >
> >
> > - Is there a name for Mellanox maintainer?

I will be the maintainer of Mellanox tree. 

> >
> > - What do other vendors, mentioned above, thinks about creating their
> > own sub-tree?
> >
> > - Are the vendor sub-trees and their maintainers need to be approved
> > by tech-board?
> >
> >
> > And what I understand from vendor specific sub-trees is, instead of
> > driver patches going into next-net directly, they will go into vendor
> > tree and next-net will pull from them.

We need to define this more carefully.
Sometimes a patchset has driver patches but also some patches for ethdev and testpmd/example.

What if other vendor would like to use those patches?
How frequent will be the merging between the vendor-specific tree and next-net? 

Am not saying there is an issue here, just need to define the rules. 

> >
> > This will distribute the maintenance work among the vendors, also will
> > give more control to vendors on their patches.
> >
> >
> > Thanks,
> > ferruh
> >
> >
> > [1]
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k
> > .org%2Fml%2Farchives%2Fdev%2F2017-
> September%2F075094.html&data=02%7C01
> >
> %7Cshahafs%40mellanox.com%7Cb9cdfab0a0544608bd4708d511c9597f%7Ca
> 652971
> >
> c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636434478859873082&sdata=A15
> iL0two
> > 9nLROmTBRUf54xCZxn%2BwLCAuZNLLyNnTqE%3D&reserved=0
> >
> > [2]
> >
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k
> > .org%2Fml%2Farchives%2Fdev%2F2017-
> October%2F078277.html&data=02%7C01%7
> >
> Cshahafs%40mellanox.com%7Cb9cdfab0a0544608bd4708d511c9597f%7Ca652
> 971c7
> >
> d2e4d9ba6a4d149256f461b%7C0%7C0%7C636434478859873082&sdata=%2B9
> tWsEXRf
> > PDZJfPqYrcRCuYmRCB3Ix7I%2FzjGwHZNbSI%3D&reserved=0
> >
> 
> Using correct mail address for Thomas.

  parent reply	other threads:[~2017-10-15  5:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 23:29 Ferruh Yigit
2017-10-12 23:31 ` Ferruh Yigit
2017-10-12 23:51   ` Thomas Monjalon
2017-10-13  5:22     ` Hemant Agrawal
2017-10-15  5:28   ` Shahaf Shuler [this message]
2017-10-16  4:49     ` Ferruh Yigit

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=VI1PR05MB31493ABD23E0E9955B6755A9C34E0@VI1PR05MB3149.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=gaetan.rivet@6wind.com \
    --cc=helin.zhang@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=heqing.zhu@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.mcnamara@intel.com \
    --cc=olgas@mellanox.com \
    --cc=pascal.mazon@6wind.com \
    --cc=thomas@monjalon.net \
    --cc=vincent.jardin@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).