DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] vmxnet3: functionality enhancements
Date: Fri, 11 Jul 2014 15:12:58 +0200	[thread overview]
Message-ID: <87818433.inX3N0OHoQ@xps13> (raw)
In-Reply-To: <20140711060338.05bbd785@samsung-9>

Hi Stephen,

2014-07-11 06:03, Stephen Hemminger:
> On Thu, 19 Jun 2014 23:02:30 -0700
> 
> Stephen Hemminger <stephen@networkplumber.org> wrote:
> > This set of patches adds new functionality to VMXNET3 and
> > removes some dead code, and fixes a memory leak.
> > 
> > These patches assume that the earlier VMXNET3 cleanup patches
> > sent to the mailing list are already merged (they haven't been yet).
> 
> Why were these patches totally ignored for 1.7.0 release?
> They include bugfixes and other stuff that was broken in the
> Intel driver. We even found more.

This patchset brought some new functionalities and was some post after the 
feature freeze.
As already said (http://dpdk.org/ml/archives/announce/2014-June/000030.html), 
it should go now in master for 1.7.1 cycle.
It would be good to have some reviews on these patches.

> If patches are going to be ignored, why should bother sending them?

They weren't ignored, but you seem to ignore the announce emails.
Please keep cool and let's continue the good work.
-- 
Thomas

      reply	other threads:[~2014-07-11 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140620060230.300986830@networkplumber.org>
2014-07-11 13:03 ` Stephen Hemminger
2014-07-11 13:12   ` Thomas Monjalon [this message]

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=87818433.inX3N0OHoQ@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 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).