From: Krzysztof Halasa <khc@pm.waw.pl>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Kevin Curtis <kevin.curtis@farsite.co.uk>,
netdev@vger.kernel.org
Subject: Re: [PATCH 10/19] drivers/net/wan: Use PCI_VDEVICE
Date: Sun, 28 Jun 2009 13:43:04 +0200 [thread overview]
Message-ID: <m3y6rcfut3.fsf@intrepid.localdomain> (raw)
In-Reply-To: <f333b1dcffc974f1df83e8d005f61a710604b8b6.1245906152.git.joe@perches.com> (Joe Perches's message of "Wed\, 24 Jun 2009 22\:13\:26 -0700")
Joe Perches <joe@perches.com> writes:
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/net/wan/farsync.c | 21 +++++++--------------
> drivers/net/wan/pc300_drv.c | 12 ++++++------
> drivers/net/wan/pc300too.c | 12 ++++--------
> drivers/net/wan/wanxl.c | 9 +++------
> 4 files changed, 20 insertions(+), 34 deletions(-)
Looks good.
Though I guess I'd delete these now unnecessary empty lines if I were
you:
> +++ b/drivers/net/wan/farsync.c
> @@ -528,26 +528,19 @@ static int fst_debug_mask = { FST_DEBUG };
> * PCI ID lookup table
> */
> static struct pci_device_id fst_pci_dev_id[] __devinitdata = {
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_T2P, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_T2P},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_T2P), FST_TYPE_T2P},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_T4P, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_T4P},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_T4P), FST_TYPE_T4P},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_T1U, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_T1U},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_T1U), FST_TYPE_T1U},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_T2U, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_T2U},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_T2U), FST_TYPE_T2U},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_T4U, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_T4U},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_T4U), FST_TYPE_T4U},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_TE1, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_TE1},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_TE1), FST_TYPE_TE1},
>
> - {PCI_VENDOR_ID_FARSITE, PCI_DEVICE_ID_FARSITE_TE1C, PCI_ANY_ID,
> - PCI_ANY_ID, 0, 0, FST_TYPE_TE1},
> + {PCI_VDEVICE(FARSITE, PCI_DEVICE_ID_FARSITE_TE1C), FST_TYPE_TE1},
> {0,} /* End */
> };
The rest of WAN bits - ack.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-06-28 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1245906151.git.joe@perches.com>
2009-06-25 5:13 ` [PATCH 02/19] drivers/atm: Use PCI_VDEVICE Joe Perches
2009-06-25 5:13 ` [PATCH 10/19] drivers/net/wan: " Joe Perches
2009-06-28 11:43 ` Krzysztof Halasa [this message]
[not found] ` <cover.1245906151.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2009-06-25 5:13 ` [PATCH 11/19] drivers/net/wireless: " Joe Perches
[not found] ` <10b896c1a1e1f65a4a342ee5aa3452ab8cb43dfb.1245906152.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2009-06-25 20:30 ` reinette chatre
2009-06-25 5:13 ` [PATCH 12/19] drivers/net: " Joe Perches
2009-06-25 5:50 ` David Dillow
2009-06-25 6:19 ` Grant Grundler
2009-06-25 12:24 ` Daniele Venzano
2009-06-25 13:52 ` Jens Osterkamp
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=m3y6rcfut3.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=joe@perches.com \
--cc=kevin.curtis@farsite.co.uk \
--cc=linux-kernel@vger.kernel.org \
--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