public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
	R.E.Wolff@BitWizard.nl
Subject: Re: [Ubuntu PATCH] Add Specialix IO8+ card support hotplug support
Date: Tue, 11 Jul 2006 12:23:02 +0200	[thread overview]
Message-ID: <20060711102302.GD26621@bitwizard.nl> (raw)
In-Reply-To: <44A98274.2010904@oracle.com>

On Mon, Jul 03, 2006 at 01:47:48PM -0700, Randy Dunlap wrote:
> Patch Description:
> Add "Specialix IO8+ card support" hotplug support

Looks good (untested). 

	Roger. 

> 
> patch location:
> http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-dapper.git;a=commitdiff;h=d795cfc591bb44f6b3d86d8f054a227cecb44bb4
> 
> ---
>  drivers/char/specialix.c |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> --- linux-2617-g21.orig/drivers/char/specialix.c
> +++ linux-2617-g21/drivers/char/specialix.c
> @@ -2584,6 +2584,13 @@ static void __exit specialix_exit_module
>  	func_exit();
>  }
>  
> +static struct pci_device_id specialx_pci_tbl[] __devinitdata = {
> +	{ PCI_VENDOR_ID_SPECIALIX, PCI_DEVICE_ID_SPECIALIX_IO8,
> +	  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
> +	{ }
> +};
> +MODULE_DEVICE_TABLE(pci, specialx_pci_tbl);
> +
>  module_init(specialix_init_module);
>  module_exit(specialix_exit_module);
>  
> 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

      reply	other threads:[~2006-07-11 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 20:47 [Ubuntu PATCH] Add Specialix IO8+ card support hotplug support Randy Dunlap
2006-07-11 10:23 ` Rogier Wolff [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=20060711102302.GD26621@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.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