DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] volunteer to be the maintainer of driver/net/intel sub-tree
Date: Thu, 22 Oct 2015 02:49:50 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909020A1938@shsmsx102.ccr.corp.intel.com> (raw)

Hi all,
Following the discussion of DPDK user space and the maintenance of development sub-trees, I'd like to volunteer myself to be the maintainer of sub-tree driver/net/intel. It includes all the PMD of Intel NICs. And Helin can be my backup.
I suggest we create a new directory to move the driver/net/e1000, driver/net/fm10k... to it. And we can also create directories for other vendors just like the kernel driver do.

Additionally, as we observed, some patch sets will not only change the files in drivers/net, but also some files in lib/librte_ether, doc, app, examples... Only being drivers/net/intel maintainer cannot work for these patch sets, especially for the new features. Applying partial feature patch set is not ideal. Ideally we need a maintainer to drive the RTE_ETHER discussion. Maybe Bruce can be a top-level maintainer. So, he can help when we face this scenario.

Best regards
Wenzhuo Lu

             reply	other threads:[~2015-10-22  2:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22  2:49 Lu, Wenzhuo [this message]
2015-10-22  8:17 ` Thomas Monjalon
2015-10-22 12:00   ` Lu, Wenzhuo

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=6A0DE07E22DDAD4C9103DF62FEBC0909020A1938@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).