From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Zhu, Heqing" <heqing.zhu@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK patch backlog
Date: Fri, 16 Oct 2015 13:08:51 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09090209FB05@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAD16F236028A64DBBC0158B1636EA4511C37444@SHSMSX103.ccr.corp.intel.com>
Hi Hemminger,
+1
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhu, Heqing
> Sent: Friday, October 16, 2015 10:47 AM
> To: Stephen Hemminger; Thomas Monjalon
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK patch backlog
>
> +1
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Friday, October 16, 2015 5:44 AM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] DPDK patch backlog
>
> There are currently 428 patches in New state in DPDK patchwork.
>
> Thomas, could you start reducing that backlog?
> 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.
I think Thomas still needs some reason. Would you like to ack my patches for e1000 base driver :)
next prev parent reply other threads:[~2015-10-16 13:08 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 [this message]
2015-10-16 8:45 ` Thomas Monjalon
2015-10-16 14:25 ` Neil Horman
2015-10-22 1:35 ` Qiu, Michael
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=6A0DE07E22DDAD4C9103DF62FEBC09090209FB05@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=heqing.zhu@intel.com \
--cc=stephen@networkplumber.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).