that a user might want to run multiple
times (e.g. after adding scsi devices?) - why should loading a module be used
for this?
--
Simon Arlott
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On 15/05/07 13:02, Matthew Wilcox wrote:
On Tue, May 15, 2007 at 12:26:29PM +0100, Simon Arlott wrote:
I've already suggested a sysfs attribute - or something equivalent - would
be much better. It's just one function that a user might want to run multiple
times (e.g. after adding scsi devices
if such
a SCSI driver module is actually selected. Why can't it at least be a
visible option in the menu? (Although even then it looks like it's
impossible to disable).
Why does ATA select SCSI anyway? Surely PATA doesn't require it?
--
Simon Arlott
-
To unsubscribe from this list: send the line
On 13/05/07 18:48, James Bottomley wrote:
On Sun, 2007-05-13 at 18:42 +0100, Simon Arlott wrote:
If you set CONFIG_MODULE=y and build SCSI we assume you could have a
SCSI driver module at some point, which would necessitate the wait scan
module.
This should be implemented like Library routines
using
a module to tell the kernel to do something? It looks like someone might
want to call scsi_complete_async_scans() more than once too - if they also
don't allow modules to be unloaded then they can't.
--
Simon Arlott
-
To unsubscribe from this list: send the line unsubscribe linux-scsi
' that seems to be completely hidden from
the menu too (CONFIG_SCSI_WAIT_SCAN). It depends on SCSI but I can't
disable SCSI...
--
Simon Arlott
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
6 matches
Mail list logo
