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

On Sat, Jan 11, 2003 at 05:17:20PM -0800, Mike Anderson wrote:
> 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.

I want to use this interface in driver that I can't support to the
device model yet (i.e. due to lack of eisa/vlb hardware I can't add
ldm support to them, but we have common drivers).

> 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.

I'm all for useful entries in sysfs, but what about doing that
implicitly in scsi_add_host when dev is null?  (and getting rid of the
separate __scsi_add_host)


  reply	other threads:[~2003-01-12  8:06 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
2003-01-12  8:06   ` Christoph Hellwig [this message]
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=20030112090647.A28861@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=andmike@us.ibm.com \
    --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