vmxnet3: functionality enhancements
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20140620060230.300986830-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org
Quoted 8 lines · On Thu, 19 Jun 2014 23:02:30 -0700 Stephen Hemminger…
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.
If patches are going to be ignored, why should bother sending them?
Hi Stephen,
2014-07-11 06:03, Stephen Hemminger:
Quoted 6 lines
On Thu, 19 Jun 2014 23:02:30 -0700
Quoted 3 lines · Stephen Hemminger
This set of patches adds new functionality to VMXNET3 and removes some dead code, and fixes a memory leak.
Quoted 6 lines
Quoted 2 lines
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.
Quoted 1 line
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.
Signature · 1 line
Thomas