netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Margit Schubert-While <margitsw@t-online.de>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH 4/6 Linux-2.6.7-bk13] prism54 device list cleanup
Date: Wed, 30 Jun 2004 16:18:41 -0400	[thread overview]
Message-ID: <40E32021.6040800@pobox.com> (raw)
In-Reply-To: <200406301941.19873.margitsw@t-online.de>

Margit Schubert-While wrote:
> 2004-06-28 Margit Schubert-While <margitsw@t-online.de>
> 
> * Clean up the device table
> 
> 
> ------------------------------------------------------------------------
> 
> diff -Naur linux-2.6.7-01/drivers/net/wireless/prism54/islpci_hotplug.c linux-2.6.7-02/drivers/net/wireless/prism54/islpci_hotplug.c
> --- linux-2.6.7-01/drivers/net/wireless/prism54/islpci_hotplug.c	2004-06-25 19:48:40.000000000 +0200
> +++ linux-2.6.7-02/drivers/net/wireless/prism54/islpci_hotplug.c	2004-06-25 20:14:46.000000000 +0200
> @@ -38,81 +38,111 @@
>  
>  /* In this order: vendor, device, subvendor, subdevice, class, class_mask,
>   * driver_data 
> - * Note: for driver_data we put the device's name 
>   * If you have an update for this please contact prism54-devel@prism54.org 
>   * The latest list can be found at http://prism54.org/supported_cards.php */
>  static const struct pci_device_id prism54_id_tbl[] = {
> +	/* 3COM 3CRWE154G72 Wireless LAN adapter */
>  	{
>  	 PCIVENDOR_3COM, PCIDEVICE_3COM6001,
>  	 PCIVENDOR_3COM, PCIDEVICE_3COM6001,
> -	 0, 0,
> -	 (unsigned long) "3COM 3CRWE154G72 Wireless LAN adapter"},
> +	 0, 0, 0
> +	},
> +
> +	/* D-Link Air Plus Xtreme G A1 - DWL-g650 A1 */
>  	{
>  	 PCIVENDOR_INTERSIL, PCIDEVICE_ISL3890,
>  	 PCIVENDOR_DLINK, 0x3202UL, 
> -	 0, 0,
> -	 (unsigned long) "D-Link Air Plus Xtreme G A1 - DWL-g650 A1"},
> +	 0, 0, 0
> +	},


Patch is OK, but two comments:

1) use standard constants from include/linux/pci_ids.h, not your own

2) where possible, use PCI_ANY_ID for subvendor id and subdevice id. 
Experience shows that unless the subvendor/subdevice is absolutely 
required, it should not be specified.

      reply	other threads:[~2004-06-30 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 17:41 [PATCH 4/6 Linux-2.6.7-bk13] prism54 device list cleanup Margit Schubert-While
2004-06-30 20:18 ` 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=40E32021.6040800@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=margitsw@t-online.de \
    --cc=netdev@oss.sgi.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).