From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: DPDK patch backlog
Date: Wed, 21 Oct 2015 10:25:12 +0200 [thread overview]
Message-ID: <2717598.bIV87FGGpb@xps13> (raw)
In-Reply-To: <20151020213424.696541ad@xeon-e3>
2015-10-20 21:34, Stephen Hemminger:
> Patch backlog is not getting better, now at 486.
>
> How can we break this logjam?
> Do I need to make a new "ready for merge" tree?
What would mean "ready for merge"?
A lot of patches are acked but do not compile or doc is missing.
I have the feeling it would become easier if there were mailing-list, patchwork
and git tree dedicated to some areas. What about starting with drivers/net?
next prev parent reply other threads:[~2015-10-21 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 21:44 DPDK patch backlog 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
2015-10-21 4:34 ` Stephen Hemminger
2015-10-21 8:25 ` Thomas Monjalon [this message]
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=2717598.bIV87FGGpb@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.