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/5][pull request] Intel Wired LAN Driver Updates 2015-03-20
Date: Fri, 20 Mar 2015 21:41:02 -0400 (EDT) [thread overview]
Message-ID: <20150320.214102.118150337215691503.davem@davemloft.net> (raw)
In-Reply-To: <1426899465-15789-1-git-send-email-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Fri, 20 Mar 2015 17:57:40 -0700
> This series contains updates to ixgb, e1000e, igb and igbvf.
>
> Eliezer and Todd provide patches to fix a potential issue found during code
> inspection. When bringing down an interface netif_carrier_off() should
> be one of the first things we do, since this will prevent the stack from
> queueing more packets to this interface.
>
> Yanir provides a fix for e1000e that was found in validating i219,
> where the call to e1000e_write_protect_nvm_ich8lan() is no longer
> supported in newer hardware. Access to these registers causes a
> system freeze in early steppings and is ignored in later steppings.
Looks good, pulled, thanks Jeff.
prev parent reply other threads:[~2015-03-21 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 0:57 [net-next 0/5][pull request] Intel Wired LAN Driver Updates 2015-03-20 Jeff Kirsher
2015-03-21 0:57 ` [net-next 1/5] ixgb: call netif_carrier_off early on down Jeff Kirsher
2015-03-21 0:57 ` [net-next 2/5] e1000e: " Jeff Kirsher
2015-03-21 0:57 ` [net-next 3/5] e1000e: NVM write protect access removed from SPT HW Jeff Kirsher
2015-03-21 0:57 ` [net-next 4/5] igb: use netif_carrier_off earlier when bringing if down Jeff Kirsher
2015-03-21 0:57 ` [net-next 5/5] igbvf: " Jeff Kirsher
2015-03-21 1:41 ` 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=20150320.214102.118150337215691503.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).