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: <201005161530.07363.fmhess@speakeasy.net>
Date:	Sun, 16 May 2010 15:30:04 -0400
From:	Frank Mori Hess <fmhess@...akeasy.net>
To:	Alexander Kurz <linux@...la.de>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Ian Abbott <abbotti@....co.uk>,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging/comedi: new Kconfig and Makefiles, drivers grouped by bustype.

On Saturday 15 May 2010, Alexander Kurz wrote:
> Hm, I cannot see a build-dependancy from any of the PCMCIA-Modules
> to 8255.c. All PCMCIA-modules do build and load fine without compiling
> 8255.c. There is a dependancy from das08_cs (PCMCIA) to das08 (ISA) via
> config COMEDI_DAS08_CS select COMEDI_DAS08.
> This will lead to a hidden select of COMEDI_DAS08 when
> COMEDI_ISA_DRIVERS is not enabled.
> Is there something that I have missed?

All the drivers that include 8255.h depend on the 8255 module.  They still 
compile without it because 8255.h provides stubs that automatically drop 
support for the 8255 chips from the other drivers if the 8255 module is 
not selected.  IMO, the stubs are not particularly valuable and with the 
fine-grained driver selection will just result in confused users with 
reduced functionality drivers.


Download attachment "signature.asc " of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ