From: Jeff Garzik <jeff@garzik.org>
To: Dhananjay Phadke <dhananjay@netxen.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] netxen: add pci ids
Date: Sat, 13 Sep 2008 15:30:32 -0400 [thread overview]
Message-ID: <48CC14D8.5090900@garzik.org> (raw)
In-Reply-To: <1221227714-8382-1-git-send-email-dhananjay@netxen.com>
Dhananjay Phadke wrote:
> Define old and new pci vendor and device ids.
>
> Signed-off-by: Dhananjay Phadke <dhananjay@netxen.com>
> ---
> drivers/net/netxen/netxen_nic_main.c | 18 +++++++++---------
> include/linux/pci_ids.h | 10 ++++++++++
> 2 files changed, 19 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/netxen/netxen_nic_main.c b/drivers/net/netxen/netxen_nic_main.c
> index 008fd66..0f8ea2c 100644
> --- a/drivers/net/netxen/netxen_nic_main.c
> +++ b/drivers/net/netxen/netxen_nic_main.c
> @@ -77,18 +77,18 @@ static irqreturn_t netxen_msi_intr(int irq, void *data);
>
> /* PCI Device ID Table */
> #define ENTRY(device) \
> - {PCI_DEVICE(0x4040, (device)), \
> + {PCI_DEVICE(PCI_VENDOR_ID_NETXEN, (device)), \
> .class = PCI_CLASS_NETWORK_ETHERNET << 8, .class_mask = ~0}
>
> static struct pci_device_id netxen_pci_tbl[] __devinitdata = {
> - ENTRY(0x0001),
> - ENTRY(0x0002),
> - ENTRY(0x0003),
> - ENTRY(0x0004),
> - ENTRY(0x0005),
> - ENTRY(0x0024),
> - ENTRY(0x0025),
> - ENTRY(0x0100),
> + ENTRY(PCI_DEVICE_ID_NX2031_10GXSR),
> + ENTRY(PCI_DEVICE_ID_NX2031_10GCX4),
> + ENTRY(PCI_DEVICE_ID_NX2031_4GCU),
> + ENTRY(PCI_DEVICE_ID_NX2031_IMEZ),
> + ENTRY(PCI_DEVICE_ID_NX2031_HMEZ),
> + ENTRY(PCI_DEVICE_ID_NX2031_XG_MGMT),
> + ENTRY(PCI_DEVICE_ID_NX2031_XG_MGMT2),
> + ENTRY(PCI_DEVICE_ID_NX3031),
> {0,}
> };
applied
prev parent reply other threads:[~2008-09-13 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 13:55 [PATCH] netxen: add pci ids Dhananjay Phadke
2008-09-13 19:30 ` Jeff Garzik [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=48CC14D8.5090900@garzik.org \
--to=jeff@garzik.org \
--cc=dhananjay@netxen.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;
as well as URLs for NNTP newsgroup(s).