[Matthew Kirkwood]
> +ifeq ($(CONFIG_BLK_DEV_MD),y)
> +SUB_DIRS += md
> +MOD_SUB_DIRS += md
> +else
> + ifeq ($(CONFIG_BLK_DEV_MD),m)
> + MOD_SUB_DIRS += md
>endif
> endif
>
Drop the 'else' bit; CONFIG_BLK_DEV_MD cannot be 'm'.
> +obj-n:=
> +obj- :=
These two va
In article <[EMAIL PROTECTED]>,
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> [ Btw, has autorun ever worked with non-scsi devices?
Yes, with IDE disks at least.
--
Shields.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Plea
Linus Torvalds writes:
> [ Btw, has autorun ever worked with non-scsi devices? They've mostly had
> the new initialization order for a long time.. ]
Hmm, I hope it will do, since a 2.2.17 kernel with Ingos RAID patches
works, and it'd be a shame to break all those RAID root filesystems out
ther
On Tue, 19 Sep 2000, Linus Torvalds wrote:
> > moving the software RAID drivers into drivers/md/,
> Make it so.
OK. Apply the attached diff and then:
$ mv drivers/block/{md,raid{0,1,5},xor}.c drivers/md/
and all might be well.
The Config.in should probably move at some stage too.
I'm not v
On Tue, 19 Sep 2000, Matthew Kirkwood wrote:
>
> It's probably solely an init-order thing but, short of
> moving the software RAID drivers into drivers/md/, I
> can't see an easy way to fix it.
That would probably not be a bad fix - especially as some people want to
split up xor.c into multipl
Hi,
It would appear that the changes in pre3 and pre4 break
RAID autorun. This is rather bothersome for those who
have RAIDed root filesystems.
It's probably solely an init-order thing but, short of
moving the software RAID drivers into drivers/md/, I
can't see an easy way to fix it.
cheers,
M
6 matches
Mail list logo
