From: Christoph Hellwig <hch@infradead.org>
To: linux-scsi@vger.kernel.org
Subject: Re: LDM scsi upper level updates and scsihosts parm
Date: Sat, 31 May 2003 10:32:55 +0100 [thread overview]
Message-ID: <20030531103255.A28131@infradead.org> (raw)
In-Reply-To: <20030531010844.GA25468@beaverton.ibm.com>; from andmike@us.ibm.com on Fri, May 30, 2003 at 06:08:45PM -0700
On Fri, May 30, 2003 at 06:08:45PM -0700, Mike Anderson wrote:
> The sysfs changes to allow the upper level to bind through the driver
> model interfaces breaks the usage of the scsihosts parm. I did not
> notice this the other day as I was running with one built-in driver and
> many modules.
>
> I know there are issues with using scsihosts today (i.e., does not
> work if you come in after the upper levels have inited).
>
> Are we going to remove the scsihosts parm or do we need a solution for
> this?
I think we should remove it. It's racy and we have proper ways to identify
filesysystems bz label/uuid or scsi hosts by the sysfs output nowdays.
Btw, did someone update the scsidev util to use 2.5 sysfs output?
next prev parent reply other threads:[~2003-05-31 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 1:08 LDM scsi upper level updates and scsihosts parm Mike Anderson
2003-05-31 9:32 ` Christoph Hellwig [this message]
2003-06-03 20:08 ` Christoph Hellwig
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=20030531103255.A28131@infradead.org \
--to=hch@infradead.org \
--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