linux-kernel - Kconfig Q: expressing a modularity dependency

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-next>] [day] [month] [year] [list]

Message-ID: <49E5E8D0.1090505@imap.cc>
Date:	Wed, 15 Apr 2009 16:01:52 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Kconfig Q: expressing a modularity dependency

My current attempts to port the Gigaset driver from isdn4linux
to CAPI require the following Kconfig dependency:

- If isdn4linux or kernelcapi or both are built as a module
  (CONFIG_ISDN_I4L=m || CONFIG_ISDN_CAPI=m)
  then gigaset can only be built as a module
  (CONFIG_ISDN_DRV_GIGASET depends on m).

- If neither isdn4linux nor kernelcapi ar built as a module
  (CONFIG_ISDN_I4L!=m && CONFIG_ISDN_CAPI!=m),
  including the case that neither is being built at all
  (CONFIG_ISDN_I4L=n && CONFIG_ISDN_CAPI=n),
  then gigaset may be built statically or as a module
  (all three tristate settings for CONFIG_ISDN_DRV_GIGASET are
  legal).

How is that best expressed in Kconfig?

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


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