public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] allow NULL dev argument to scsi_add_host
Date: Sat, 11 Jan 2003 17:17:20 -0800	[thread overview]
Message-ID: <20030112011720.GC1878@beaverton.ibm.com> (raw)
In-Reply-To: <20030111203317.A25836@lst.de>

Christoph Hellwig [hch@lst.de] wrote:
> We need scsi_add_host sometimes without having a struct device (i.e.
> eisa/vlb drivers, ieee1394 storage), so handle that case gracefully.
> 
> 
> --- 1.41/drivers/scsi/hosts.c	Mon Dec 16 10:59:41 2002
> +++ edited/drivers/scsi/hosts.c	Sat Jan 11 19:06:56 2003
> @@ -314,9 +314,10 @@
>   **/
>  int scsi_add_host(struct Scsi_Host *shost, struct device *dev)
>  {
> -	dev->class_data = shost;
> -	shost->host_gendev = dev;
> -
> +	if (dev) {
> +		dev->class_data = shost;
> +		shost->host_gendev = dev;
> +	}
>  	return __scsi_add_host(shost);
>  }
>  

This will cause all scsi device registers to show up in the root of the sysfs
tree. The goal was that children of the adapter would be equal to the
my_devices member. I also thought that callers of this interface would
be converted to support sysfs.

If there are going to be many pseudo adapters that do not want to go
through the overhead of creating a sysfs bus entry like ide-scsi
then maybe I should work on a sysfs SCSI sub-system like block and if
dev is null it means you are pseudo and we would create an entry for
the adapter under (? /sysfs/scsi/pseudo ?). This could then be the value
we stuff in host_gendev. Though the sysfs entry would not be much use to
the caller, but useful for SCSI.

-andmike
--
Michael Anderson
andmike@us.ibm.com


  parent reply	other threads:[~2003-01-12  1:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 19:33 [PATCH] allow NULL dev argument to scsi_add_host Christoph Hellwig
2003-01-11 22:32 ` Willem Riede
2003-01-12  1:17 ` Mike Anderson [this message]
2003-01-12  8:06   ` Christoph Hellwig
2003-01-12 19:40     ` Mike Anderson
2003-01-12 23:11       ` Andries Brouwer
2003-01-13  6:50         ` 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=20030112011720.GC1878@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@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