From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 0/7] vmxnet3: functionality enhancements Date: Fri, 11 Jul 2014 15:12:58 +0200 Message-ID: <87818433.inX3N0OHoQ@xps13> References: <20140620060230.300986830@networkplumber.org> <20140711060338.05bbd785@samsung-9> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Stephen Hemminger Return-path: In-Reply-To: <20140711060338.05bbd785@samsung-9> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Stephen, 2014-07-11 06:03, Stephen Hemminger: > On Thu, 19 Jun 2014 23:02:30 -0700 > > Stephen Hemminger 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