From: Christoph Hellwig <hch@infradead.org>
To: Kurt Garloff <garloff@suse.de>,
James Bottomley <James.Bottomley@steeleye.com>,
Andrew Morton <akpm@osdl.org>,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: Patches for SCSI scanning
Date: Tue, 20 Apr 2004 13:04:14 +0100 [thread overview]
Message-ID: <20040420130414.A24817@infradead.org> (raw)
In-Reply-To: <20040420115419.GG4356@tpkurt.garloff.de>; from garloff@suse.de on Tue, Apr 20, 2004 at 01:54:19PM +0200
> * Patch 2: Drop REPORT_LUN config option and introduce
> noreportlun and reportlun2 parameters (the latter allowing SCSI-2
> devs to be scanned with REPORT_LUNS).
I'm all for this one.
> * Patch 3: Allow host adapters to avoid REPORT_LUNS.
Alson sounds okay, do you already have drivers that would set it?
> * Patch 4: allow_ghost_devices parameter
I still think this should be a blacklist flag as it's really a spec
violation from EMC if they really don't get it right. And I still
haven't an answer why they can't work around it by setting those
magic devices online from userland.
> * Patch 5: inq_timeout parameter
Maybe this one should actually be a per-device tunable in sysfs? Sure,
to actually make use of it for the root device you'd need an initrd but
the distros do that anyway.
> Sidenote: We should drop SCSI_FORCELUN and CONFIG_SCSI_MULTI_LUN, otherwise
> people will misconfigure their kernel (such as the HP guy) and start to want
> every multi-lun device listed.
Agreed.
next prev parent reply other threads:[~2004-04-20 12:04 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 18:57 Patches for SCSI scanning Kurt Garloff
2004-04-18 23:16 ` James Bottomley
2004-04-20 11:54 ` Kurt Garloff
2004-04-20 12:04 ` Christoph Hellwig [this message]
2004-04-20 13:02 ` Kurt Garloff
2004-04-20 14:38 ` James Bottomley
2004-04-20 16:03 ` Kurt Garloff
2004-04-20 16:08 ` James Bottomley
2004-04-21 13:48 ` Kurt Garloff
2004-04-21 15:36 ` James Bottomley
2004-04-21 13:45 ` Kurt Garloff
2004-04-21 14:10 ` PATCH 1/5: scsi-scan-deprecate-forcelun Kurt Garloff
2004-04-21 14:12 ` PATCH 2/5: scsi-scan-blist_replun Kurt Garloff
2004-04-21 15:14 ` Christoph Hellwig
2004-04-21 15:30 ` Kurt Garloff
2004-04-21 16:03 ` Kurt Garloff
2004-04-21 14:13 ` PATCH 3/5: scsi-scan-no-offl-pq-notcon Kurt Garloff
2004-04-21 14:14 ` PATCH 4/5: scsi-scan-dont-att-pq-notcon Kurt Garloff
2004-04-21 15:02 ` Christoph Hellwig
2004-04-21 15:24 ` Kurt Garloff
2004-04-21 15:33 ` Mike Anderson
2004-04-21 15:33 ` Christoph Hellwig
2004-04-21 16:08 ` Kurt Garloff
2004-04-21 16:18 ` James Bottomley
2004-04-21 16:55 ` Patrick Mansfield
2004-04-21 22:51 ` Kurt Garloff
2004-04-22 20:39 ` Patrick Mansfield
2004-04-22 20:45 ` James Bottomley
2004-04-21 16:58 ` Kurt Garloff
2004-04-21 16:16 ` Kurt Garloff
2004-04-21 15:40 ` James Bottomley
2004-04-21 14:14 ` PATCH 5/5: scsi-scan-inq-timeout Kurt Garloff
2004-04-21 20:24 ` Patrick Mansfield
2004-04-21 22:48 ` Kurt Garloff
2004-04-21 23:49 ` Patrick Mansfield
2004-04-20 16:26 ` Patches for SCSI scanning Patrick Mansfield
2004-04-20 16:42 ` Kurt Garloff
2004-04-20 17:44 ` Patrick Mansfield
2004-04-21 13:52 ` Kurt Garloff
2004-04-20 10:24 ` Fabien Salvi
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 4:09 Martin Peschke3
2004-04-22 4:17 Martin Peschke3
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=20040420130414.A24817@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=garloff@suse.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