From: Jesper Dangaard Brouer <jdb@comx.dk>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [net-next] ixgbe: Add module parameter to allow untested and unsafe SFP+ modules
Date: Wed, 01 Feb 2012 20:35:16 +0100 [thread overview]
Message-ID: <1328124916.12731.0.camel@probook> (raw)
In-Reply-To: <1328123961-17237-1-git-send-email-jeffrey.t.kirsher@intel.com>
On Wed, 2012-02-01 at 11:19 -0800, Jeff Kirsher wrote:
> From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
>
> The X520 family of network devices, with the 82599 chip, support a
> small number of Intel-verified SFP+ modules on their NICs. To maintain
> stability and quality, the current devices restrict untested 3rd party
> SFP+ modules.
>
> This patch introduces a module parameter for ixgbe to allow these untested
> modules at the user's peril. It also includes a warning to the syslog
> alerting users that the modules aren't supported, and results may
> vary.
>
> CC: Jesper Dangaard Brouer <hawk@comx.dk>
> Signed-off-by: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
> Tested-by: Phil Schmitt <phillip.j.schmitt@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Acked-by: Jesper Dangaard Brouer <hawk@comx.dk>
prev parent reply other threads:[~2012-02-01 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 19:19 [net-next] ixgbe: Add module parameter to allow untested and unsafe SFP+ modules Jeff Kirsher
2012-02-01 19:24 ` David Miller
2012-02-01 19:35 ` Jesper Dangaard Brouer [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=1328124916.12731.0.camel@probook \
--to=jdb@comx.dk \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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).