All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20190529093548.3df7ee73@hermes.lan>

diff --git a/a/content_digest b/N1/content_digest
index 695de77..09b6bb8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,9 +3,15 @@
  "ref\0eb730f01-0c6d-0589-36cc-7193d64c1ee8@molgen.mpg.de\0"
  "ref\0CANn89i+VvwMaHy2Br-0CcC3gPQ+PmG3Urpn4KpqL0P7XBykmcw@mail.gmail.com\0"
  "From\0Stephen Hemminger <stephen@networkplumber.org>\0"
- "Subject\0[Intel-wired-lan] Driver has suspect GRO implementation, TCP performance may be compromised.\0"
+ "Subject\0Re: Driver has suspect GRO implementation, TCP performance may be compromised.\0"
  "Date\0Wed, 29 May 2019 09:35:48 -0700\0"
- "To\0intel-wired-lan@osuosl.org\0"
+ "To\0Eric Dumazet <edumazet@google.com>\0"
+ "Cc\0Paul Menzel <pmenzel@molgen.mpg.de>"
+  Eric Dumazet <eric.dumazet@gmail.com>
+  Jeff Kirsher <jeffrey.t.kirsher@intel.com>
+  intel-wired-lan@lists.osuosl.org
+  netdev <netdev@vger.kernel.org>
+ " Linux Kernel Mailing List <linux-kernel@vger.kernel.org>\0"
  "\00:1\0"
  "b\0"
  "On Wed, 29 May 2019 09:00:54 -0700\n"
@@ -102,4 +108,4 @@
  "There always some confusion in Linux about whether MTU is transmit only or devices\n"
  have to enforce it on receive.
 
-1904c3f00cec31e6ee4af9b71a8dc69db803648ee085511f5c8e89ebc0675d46
+2763df3b3f98c40da987517028b6bd15ac8c1e7528672fea249570206c021556

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.