DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <shemming@brocade.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Patches outstanding
Date: Tue, 17 Feb 2015 16:59:48 +0100	[thread overview]
Message-ID: <17608680.v5jvXcnVee@xps13> (raw)
In-Reply-To: <20150217103507.7da72f1a@uryu.home.lan>

2015-02-17 10:35, Stephen Hemminger:
> There are currently 1039 patches outstanding on DPDK.
> What is the schedule for getting these merged or resolved?

Several patches are ready to be applied in coming days.
Many patches are still waiting for closing discussions.

> I don't think it would be reasonable to declare 2.0 as done
> until the patch backlog is 0!

The target is to integrate features in next days and make a rc1.
Then we will have 5 weeks to fix and clean before the release.

If some patches have not reached a consensus at the proper time,
they could stay in the backlog.

  reply	other threads:[~2015-02-17 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 15:35 Stephen Hemminger
2015-02-17 15:59 ` Thomas Monjalon [this message]
2015-02-19 13:08 ` Neil Horman
2015-02-19 13:46   ` Thomas Monjalon
2015-02-19 15:15     ` O'driscoll, Tim

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=17608680.v5jvXcnVee@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=shemming@brocade.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).