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, guru.anbalagane@oracle.com
Subject: Re: [net-next 00/10][pull request] 1GbE Intel Wired LAN Driver Updates 2017-01-06
Date: Fri, 06 Jan 2017 16:05:52 -0500 (EST) [thread overview]
Message-ID: <20170106.160552.567069248874279723.davem@davemloft.net> (raw)
In-Reply-To: <20170106104852.10363-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Fri, 6 Jan 2017 02:48:42 -0800
> This series contains updates/fixes to igb and e1000e.
Pulled, thanks Jeff.
prev parent reply other threads:[~2017-01-06 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 10:48 [net-next 00/10][pull request] 1GbE Intel Wired LAN Driver Updates 2017-01-06 Jeff Kirsher
2017-01-06 10:48 ` [net-next 01/10] igb: Realign bad indentation Jeff Kirsher
2017-01-06 10:48 ` [net-next 02/10] e1000e: driver trying to free already-free irq Jeff Kirsher
2017-01-06 10:48 ` [net-next 03/10] igb: correct register comments Jeff Kirsher
2017-01-06 10:48 ` [net-next 04/10] igb: Workaround for igb i210 firmware issue Jeff Kirsher
2017-01-06 10:48 ` [net-next 05/10] igb: use igb_adapter->io_addr instead of e1000_hw->hw_addr Jeff Kirsher
2017-01-06 10:48 ` [net-next 06/10] igb: reset the PHY before reading the PHY ID Jeff Kirsher
2017-01-06 10:48 ` [net-next 07/10] igb: re-assign hw address pointer on reset after PCI error Jeff Kirsher
2017-01-06 10:48 ` [net-next 08/10] igb: close/suspend race in netif_device_detach Jeff Kirsher
2017-01-06 10:48 ` [net-next 09/10] igb: add i211 to i210 PHY workaround Jeff Kirsher
2017-01-06 10:48 ` [net-next 10/10] igb: Fix hw_dbg logging in igb_update_flash_i210 Jeff Kirsher
2017-01-06 21:05 ` 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=20170106.160552.567069248874279723.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=guru.anbalagane@oracle.com \
--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).