On Tue, May 15, 2007 01:41, Satyam Sharma wrote:
> On 5/14/07, James Bottomley <[EMAIL PROTECTED]> wrote:
>> On Mon, 2007-05-14 at 17:53 +0530, Satyam Sharma wrote:
>> > > I guess this is probably the behaviour that James wanted originally?
>>
>> No ... you're still not reading the explanation in t
On 5/14/07, James Bottomley <[EMAIL PROTECTED]> wrote:
On Mon, 2007-05-14 at 17:53 +0530, Satyam Sharma wrote:
> > I guess this is probably the behaviour that James wanted originally?
No ... you're still not reading the explanation in the thread:
The wait scan module is designed to wait for sca
On May 14 2007 19:46, Alan Cox wrote:
>> On May 13 2007 12:48, James Bottomley wrote:
>> >
>> >> Why does ATA select SCSI anyway? Surely PATA doesn't require it?
>> >That's a bit offtopic and to the wrong list.
>> >libata-pata does require SCSI ...
>>
>> And in the long run, that SCSI parts which
On Mon, 14 May 2007 19:29:12 +0200 (MEST)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>
> On May 13 2007 12:48, James Bottomley wrote:
> >
> >> Why does ATA select SCSI anyway? Surely PATA doesn't require it?
> >
> >That's a bit offtopic and to the wrong list.
> >
> >libata-pata does require SCSI .
On May 13 2007 12:48, James Bottomley wrote:
>
>> Why does ATA select SCSI anyway? Surely PATA doesn't require it?
>
>That's a bit offtopic and to the wrong list.
>
>libata-pata does require SCSI ...
And in the long run, that SCSI parts which are actually used by ATA
should be factored out so tha
On Mon, 2007-05-14 at 17:53 +0530, Satyam Sharma wrote:
> > I guess this is probably the behaviour that James wanted originally?
No ... you're still not reading the explanation in the thread:
The wait scan module is designed to wait for scans of driver modules.
Whether SCSI=y or m has no effect o
Hello,
> > [...]
> > config SCSI_WAIT_SCAN
> > tristate
> > - default m
> > - depends on SCSI
> > - depends on MODULES
> > + default m if SCSI=m
> > + default n
>
> Note that this also means SCSI_WAIT_SCAN=n (will not get compiled
> and built even as a modul
Hello,
> [...]
> config SCSI_WAIT_SCAN
> tristate
> - default m
> - depends on SCSI
> - depends on MODULES
> + default m if SCSI=m
> + default n
Note that this also means SCSI_WAIT_SCAN=n (will not get compiled
and built even as a module) if SCSI=y. But th
On 5/14/07, Satyam Sharma <[EMAIL PROTECTED]> wrote:
[...]
config SCSI_WAIT_SCAN
tristate
- default m
- depends on SCSI
- depends on MODULES
+ default m if SCSI=m
+ default n
Note that this also means SCSI_WAIT_SCAN=n (will not get compiled
and built even
Hi,
On 5/13/07, James Bottomley <[EMAIL PROTECTED]> wrote:
On Sun, 2007-05-13 at 11:10 -0500, James Bottomley wrote:
> > - depends on SCSI
> > + depends on SCSI_SCAN_ASYNC
This is incorrect, alright, but not because of any of the reasons James
mentions below.
The only reason why some modu
On 13/05/07 17:10, James Bottomley wrote:
On Sun, 2007-05-13 at 12:06 -0400, Dave Jones wrote:
diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index e62d23f..0f6c370 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -244,7 +244,7 @@ config SCSI_SCAN_ASYNC
config SCSI_WAIT
On Sun, 2007-05-13 at 19:26 +0100, Simon Arlott wrote:
> 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 th
On Sun, May 13, 2007 at 07:26:31PM +0100, Simon Arlott wrote:
> It looks like SCSI_WAIT_SCAN is pointless unless SCSI_SCAN_ASYNC
> is selected - so it should depend on it:
>
> ---
> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> index e62d23f..0f6c370 100644
> --- a/drivers/sc
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"
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" and only added if such
> a
On 13/05/07 17:27, James Bottomley wrote:
On Sun, 2007-05-13 at 12:20 -0400, Robert P. J. Day wrote:
since this thread looks like it's going to get away from me in a
hurry :-), my only point in asking was to point out that that lone
module was the only thing preventing the build from being modul
On Sun, 13 May 2007, James Bottomley wrote:
> On Sun, 2007-05-13 at 12:20 -0400, Robert P. J. Day wrote:
> > since this thread looks like it's going to get away from me in a
> > hurry :-), my only point in asking was to point out that that lone
> > module was the only thing preventing the build fr
On Sun, May 13, 2007 at 11:10:55AM -0500, James Bottomley wrote:
> > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> > index e62d23f..0f6c370 100644
> > --- a/drivers/scsi/Kconfig
> > +++ b/drivers/scsi/Kconfig
> > @@ -244,7 +244,7 @@ config SCSI_SCAN_ASYNC
> > config SCSI_WAIT_S
On Sun, May 13, 2007 at 11:18:35AM -0500, James Bottomley wrote:
> On Sun, 2007-05-13 at 11:10 -0500, James Bottomley wrote:
> > > -depends on SCSI
> > > +depends on SCSI_SCAN_ASYNC
> >
> > No. SCSI_SCAN_ASYNC is a bool ... if you depend on it, you'll force the
> > wait scan
On Sun, 2007-05-13 at 12:20 -0400, Robert P. J. Day wrote:
> since this thread looks like it's going to get away from me in a
> hurry :-), my only point in asking was to point out that that lone
> module was the only thing preventing the build from being module-free.
>
> i'm not saying that that's
On Sun, 13 May 2007, James Bottomley wrote:
> On Sun, 2007-05-13 at 12:06 -0400, Dave Jones wrote:
> > On Sun, May 13, 2007 at 11:22:55AM -0400, Robert P. J. Day wrote:
> > >
> > > not a big deal, but is there a reason that a "make defconfig" on my
> > > x86 system ends up selecting and build
On Sun, 2007-05-13 at 11:10 -0500, James Bottomley wrote:
> > - depends on SCSI
> > + depends on SCSI_SCAN_ASYNC
>
> No. SCSI_SCAN_ASYNC is a bool ... if you depend on it, you'll force the
> wait scan to be built in, which isn't the idea at all.
Plus SCSI_SCAN_ASYNC only sets the *default* f
On Sun, 2007-05-13 at 12:06 -0400, Dave Jones wrote:
> On Sun, May 13, 2007 at 11:22:55AM -0400, Robert P. J. Day wrote:
> >
> > not a big deal, but is there a reason that a "make defconfig" on my
> > x86 system ends up selecting and building a single module?
> >
> > Building modules, st
On Sun, May 13, 2007 at 11:22:55AM -0400, Robert P. J. Day wrote:
>
> not a big deal, but is there a reason that a "make defconfig" on my
> x86 system ends up selecting and building a single module?
>
> Building modules, stage 2.
> MODPOST 1 modules
> CC drivers/scsi/scsi_wait
24 matches
Mail list logo
