linux-kernel - Re: Reenable SCSI=m

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061005130921.GF16812@stusta.de>
Date:	Thu, 5 Oct 2006 15:09:21 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Andreas Schwab <schwab@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Reenable SCSI=m

On Thu, Oct 05, 2006 at 02:44:28PM +0200, Andreas Schwab wrote:

> Since CONFIG_SCSI (a tristate) now depends on CONFIG_BLOCK (a bool) it is
> no longer possible to set CONFIG_SCSI=m.
>...

A tristate depending on a bool is a common case that works just fine and 
allows the modular setting.

And CONFIG_SCSI=m is possible in 2.6.19-rc1.

What exactly is the problem you observed?

> Andreas.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/