linux-kernel - #ifdef CONFIG_ checks not working

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: <47266B0D-0A99-4C5F-BA85-FCC8986E8862@mac.com>
Date:	Tue, 26 Oct 2010 18:28:22 +0400
From:	Elvis Dowson <elvis.dowson@....com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Luciano Coelho <luciano.coelho@...ia.com>
Subject: #ifdef CONFIG_ checks not working

Hi,
       I just noticed that with the 2.6.36-rc8 kernel, the #ifdef checks aren't working. 

So for example, if I add the following code fragment in my omap3_beagle_init function, CONFIG_WL1271 doesn't get detected, even though in my .config file, CONFIG_WL1271=m.

This way, the mux settings might also fail, right, which might be the source of a few of the problems that I'm facing. 

Would you happen to know why this is not working. This type of checks used to work with the 2.6.32 kernel versions.

#ifdef CONFIG_WL1271
    printk(KERN_INFO "%s: CONFIG_WL1271 detected\n", __func__);
#else
    printk(KERN_INFO "%s: CONFIG_WL1271 not detected\n", __func__);
#endif

Boot message: 

[    0.000000] omap3_beagle_init: CONFIG_WL1271 not detected

Best regards,

Elvis Dowson

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