From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 0/9][pull request] 1GbE Intel Wired LAN Driver Updates 2017-10-10
Date: Tue, 10 Oct 2017 13:21:36 -0700 (PDT) [thread overview]
Message-ID: <20171010.132136.177905337420469413.davem@davemloft.net> (raw)
In-Reply-To: <20171010172139.77914-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Tue, 10 Oct 2017 10:21:30 -0700
> This series contains updates to e1000e and igb.
Pulled, thanks Jeff.
prev parent reply other threads:[~2017-10-10 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:21 [net-next 0/9][pull request] 1GbE Intel Wired LAN Driver Updates 2017-10-10 Jeff Kirsher
2017-10-10 17:21 ` [net-next 1/9] e1000e: Fix error path in link detection Jeff Kirsher
2017-10-10 17:21 ` [net-next 2/9] e1000e: Fix wrong comment related to " Jeff Kirsher
2017-10-10 17:21 ` [net-next 3/9] e1000e: Fix return value test Jeff Kirsher
2017-10-10 17:21 ` [net-next 4/9] e1000e: Separate signaling for link check/link up Jeff Kirsher
2017-10-10 17:21 ` [net-next 5/9] e1000e: Avoid receiver overrun interrupt bursts Jeff Kirsher
2017-10-10 17:21 ` [net-next 6/9] e1000e: fix buffer overrun while the I219 is processing DMA transactions Jeff Kirsher
2017-10-11 9:07 ` David Laight
2017-10-16 10:24 ` Neftin, Sasha
2017-10-16 16:11 ` Alexander Duyck
2017-10-16 10:39 ` Neftin, Sasha
2017-10-16 13:27 ` David Laight
2017-10-10 17:21 ` [net-next 7/9] e1000e: apply burst mode settings only on default Jeff Kirsher
2017-10-10 17:21 ` [net-next 8/9] e1000e: Be drop monitor friendly Jeff Kirsher
2017-10-10 17:21 ` [net-next 9/9] igb: check memory allocation failure Jeff Kirsher
2017-10-10 20:21 ` David Miller [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=20171010.132136.177905337420469413.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
/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).