From: Edward Cree <ecree@solarflare.com>
To: <linux-net-drivers@solarflare.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH net-next 3/6] sfc: add Medford2 (SFC9250) PCI Device IDs
Date: Mon, 18 Dec 2017 16:56:34 +0000 [thread overview]
Message-ID: <e531c996-e42b-54b4-ac0c-69c9c5bfcfe4@solarflare.com> (raw)
In-Reply-To: <f9e1279b-03d0-729c-2518-c1e204444447@solarflare.com>
Signed-off-by: Edward Cree <ecree@solarflare.com>
---
drivers/net/ethernet/sfc/efx.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/net/ethernet/sfc/efx.c b/drivers/net/ethernet/sfc/efx.c
index e50049cba50b..7bcbedce07a5 100644
--- a/drivers/net/ethernet/sfc/efx.c
+++ b/drivers/net/ethernet/sfc/efx.c
@@ -2910,6 +2910,10 @@ static const struct pci_device_id efx_pci_table[] = {
.driver_data = (unsigned long) &efx_hunt_a0_nic_type},
{PCI_DEVICE(PCI_VENDOR_ID_SOLARFLARE, 0x1a03), /* SFC9220 VF */
.driver_data = (unsigned long) &efx_hunt_a0_vf_nic_type},
+ {PCI_DEVICE(PCI_VENDOR_ID_SOLARFLARE, 0x0b03), /* SFC9250 PF */
+ .driver_data = (unsigned long) &efx_hunt_a0_nic_type},
+ {PCI_DEVICE(PCI_VENDOR_ID_SOLARFLARE, 0x1b03), /* SFC9250 VF */
+ .driver_data = (unsigned long) &efx_hunt_a0_vf_nic_type},
{0} /* end of list */
};
next prev parent reply other threads:[~2017-12-18 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 16:54 [PATCH net-next 0/6] sfc: Initial X2000-series (Medford2) support Edward Cree
2017-12-18 16:55 ` [PATCH net-next 1/6] sfc: make mem_bar a function rather than a constant Edward Cree
2017-12-18 16:56 ` [PATCH net-next 2/6] sfc: support VI strides other than 8k Edward Cree
2017-12-18 16:56 ` Edward Cree [this message]
2017-12-18 16:56 ` [PATCH net-next 4/6] sfc: improve PTP error reporting Edward Cree
2017-12-18 16:57 ` [PATCH net-next 5/6] sfc: update EF10 register definitions Edward Cree
2017-12-18 16:57 ` [PATCH net-next 6/6] sfc: populate the timer reload field Edward Cree
2017-12-18 18:16 ` [PATCH net-next 0/6] sfc: Initial X2000-series (Medford2) support David Miller
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=e531c996-e42b-54b4-ac0c-69c9c5bfcfe4@solarflare.com \
--to=ecree@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
/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