I was looking through recent changes in e1000e, and thought these might be suitable for inclusion in stable updates:
commit 493004d04f56fd7d642bdbb2938e17e5f7d622d1
Author: David Ertman <david.m.ert...@intel.com>
Date: Fri Jul 4 01:44:32 2014 +0000
e1000e: Fix CRC errors with jumbo traffic
commit 47ccd1edc57ddabb81f6ba07e1e30201a8f578d6
Author: Vlad Yasevich <vyasev...@gmail.com>
Date: Mon Aug 25 10:34:48 2014 -0400
e1000e: Fix TSO with non-accelerated vlans
commit 6930895df994af212985396f1274712aaaa5bc26
Author: Mathias Koehrer <mathias.koeh...@etas.com>
Date: Thu Aug 7 18:51:53 2014 +0000
e1000e: Fix 82572EI that has no hardware timestamp support
This is purely based on the commit messages, not on bug reports or my
own experience of the bugs. I leave it to the e1000e maintainers to
judge whether they're important enough.
Ben.
--
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
