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] [day] [month] [year] [list]
Date:	Thu, 21 Sep 2006 07:54:56 +0200
From:	Pierre Ossman <drzeus-list@...eus.cx>
To:	Alex Dubov <oakad@...oo.com>
CC:	linux-kernel@...r.kernel.org, rmk+lkml@....linux.org.uk
Subject: Re: [PATCH 2/2] [MMC] Driver for TI FlashMedia card reader - Kconfig/Makefile
 entries

Alex Dubov wrote:
>
> I kind of fail to follow here. Do you want to switch TIFM_CORE -> MMC_TIFM_SD dependency into
> MMC_TIFM_SD -> TIFM_CORE + TIFM_7XX1 one? It may be slightly more convenient for users (even
> though most are using pre-compiled kernels provided by distribution), but will be logically
> incorrect, doesn't it? And then, what will become of memorystick driver?
>
>   

No no, I want a change from "depends" to "select". That symbolises the
same dependency, but it has slightly different semantics (which it
probably shouldn't, but that's another discussion). With "depends", a
config entry is hidden if its dependencies aren't satisfied. With
"select", it will forcefully enable those dependencies.

>From a user point of view, the former requires knowledge of how all of
these things hangs together (which is expecting a bit much), but the
latter will automatically pull in all the components needed to build the
option the user selects (which is how dependencies should work IMO).

Rgds
Pierre


> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>   

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ