DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Neil Horman <nhorman@tuxdriver.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK patch backlog
Date: Thu, 22 Oct 2015 01:35:17 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028621B50203@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20151016142501.GA5602@hmsreliant.think-freely.org>

On 2015/10/16 22:25, Neil Horman wrote:
> On Fri, Oct 16, 2015 at 10:45:23AM +0200, Thomas Monjalon wrote:
>> 2015-10-15 14:44, Stephen Hemminger:
>>> There are currently 428 patches in New state in DPDK patchwork.
>>>
>>> Thomas, could you start reducing that backlog?
>> Yes
>>
>>> The simplest solution would be to merge some of the big patch series
>>> from Intel for the base drivers, then reviewers can focus on the other
>>> patches.
>> That's why having a drivers/net subtree would be useful.
>>
> Agreed, a dpdk-next tree would really be the solution here.

Can't agree more :)

Thanks,
Michael
> Neil
>
>


  reply	other threads:[~2015-10-22  1:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 21:44 Stephen Hemminger
2015-10-16  2:47 ` Zhu, Heqing
2015-10-16 13:08   ` Lu, Wenzhuo
2015-10-16  8:45 ` Thomas Monjalon
2015-10-16 14:25   ` Neil Horman
2015-10-22  1:35     ` Qiu, Michael [this message]
2015-10-21  4:34 ` Stephen Hemminger
2015-10-21  8:25   ` Thomas Monjalon
2015-10-21  8:48     ` Panu Matilainen
2015-10-21  9:03       ` Thomas Monjalon
2015-10-21 17:41         ` Matthew Hall
2015-10-23 21:39           ` Thomas Monjalon
2015-10-22  1:45         ` Qiu, Michael
2015-10-21 11:10     ` Neil Horman

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=533710CFB86FA344BFBF2D6802E6028621B50203@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    --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).