From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: "Nelson, Shannon" <shannon.nelson@intel.com>,
Stefan Assmann <sassmann@kpanic.de>,
netdev <netdev@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Subject: Re: [E1000-devel] i40e: crash on NMI by continuous module reload
Date: Fri, 27 Feb 2015 16:45:58 -0800 [thread overview]
Message-ID: <1425084358.9477.76.camel@jtkirshe-mobl> (raw)
In-Reply-To: <3DA4D8F9-C0E0-41B9-8F9C-BD17BC7A09B3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Fri, 2015-02-27 at 16:25 -0500, Nicholas Krause wrote:
> Thanks Shannon,
> For the advice on there being a newer driver and firmware to test that
> on before reporting the bug against this driver. I am curious as to
> why this newer code is not up streamed to Linux next yet through.
Because I still have ~40 patches in my queue for i40e that need to go
upstream to get the upstream driver in sync with our out-of-tree driver.
Also Nick, please do not take advantage of me being nice to you and
letting you remain on e1000-devel mailing list, even though you have
been banned on @vger.kernel.org mailing lists. It is clear from your
attempts to help Stefan, you do not know the driver and your "blind
stabs in the dark" to assist, only hinder our abilities to assist
others.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-28 0:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 13:50 i40e: crash on NMI by continuous module reload Stefan Assmann
2015-02-27 14:02 ` nick
2015-02-27 14:16 ` [E1000-devel] " Stefan Assmann
2015-02-27 14:44 ` nick
2015-02-27 19:42 ` Nelson, Shannon
2015-02-27 21:25 ` Nicholas Krause
2015-02-28 0:45 ` Jeff Kirsher [this message]
2015-02-28 2:11 ` Nicholas Krause
2015-03-02 8:08 ` [E1000-devel] " Stefan Assmann
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=1425084358.9477.76.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@kpanic.de \
--cc=shannon.nelson@intel.com \
--cc=xerofoify@gmail.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).