public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Douglas Gilbert <dougg@torque.net>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sg version 3.5.28 for lk 2.5.64
Date: Tue, 11 Mar 2003 20:09:27 +0100	[thread overview]
Message-ID: <20030311200927.A967@lst.de> (raw)
In-Reply-To: <20030311081838.A9661@beaverton.ibm.com>; from patmans@us.ibm.com on Tue, Mar 11, 2003 at 08:18:38AM -0800

On Tue, Mar 11, 2003 at 08:18:38AM -0800, Patrick Mansfield wrote:
> Is there a patch for putting the aic or all scsi_hosts into the
> shost_devclass class, like scsi_debug.c does for itself?

You're right!  This is the snipplet I missed when sending out the
aic7xxx hotplug changes (+ the same for aic79xx):


--- 1.7/drivers/scsi/aic7xxx/aic7xxx_osm_pci.c	Wed Feb 26 18:14:16 2003
+++ edited/drivers/scsi/aic7xxx/aic7xxx_osm_pci.c	Tue Mar 11 19:13:02 2003
@@ -75,10 +75,13 @@
 MODULE_DEVICE_TABLE(pci, ahc_linux_pci_id_table);
 
 struct pci_driver aic7xxx_pci_driver = {
-	name:		"aic7xxx",
-	probe:		ahc_linux_pci_dev_probe,
-	remove:		ahc_linux_pci_dev_remove,
-	id_table:	ahc_linux_pci_id_table
+	.name		= "aic7xxx",
+	.probe		= ahc_linux_pci_dev_probe,
+	.remove		= ahc_linux_pci_dev_remove,
+	.id_table	= ahc_linux_pci_id_table,
+	.driver		= {
+		.devclass	= &shost_devclass,
+	},
 };
 
 static void

  parent reply	other threads:[~2003-03-11 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 13:23 [PATCH] sg version 3.5.28 for lk 2.5.64 Douglas Gilbert
2003-03-11 14:28 ` Christoph Hellwig
2003-03-11 16:18   ` Patrick Mansfield
2003-03-11 17:34     ` Mike Anderson
2003-03-11 19:09     ` Christoph Hellwig [this message]
2003-03-12 12:54       ` Douglas Gilbert
2003-03-11 17:37   ` Mike Anderson

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=20030311200927.A967@lst.de \
    --to=hch@lst.de \
    --cc=dougg@torque.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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