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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 05 Oct 2006 16:34:40 +0200
From:	Andreas Schwab <schwab@...e.de>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Reenable SCSI=m

Adrian Bunk <bunk@...sta.de> writes:

> 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.

You are right.  My problem was that I said CONFIG_ATA=y when I meant
CONFIG_ATA=m which forced CONFIG_SCSI=y behind by back.  It didn't occur
to me that this was related.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@...e.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
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/