linux-kernel - Re: [PATCH] ARM: OMAP: Conditionally compile counter

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]

Date:	Mon, 26 Nov 2012 14:15:45 +0100
From:	Alessio Igor Bogani <alessio.bogani@...ttra.trieste.it>
To:	Igor Grinberg <grinberg@...pulab.co.il>
CC:	Tony Lindgren <tony@...mide.com>, linux-omap@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: OMAP: Conditionally compile counter_32k

Hi Igor,

On 26/11/2012 13:02, Igor Grinberg wrote:
> On 11/26/12 11:28, Alessio Igor Bogani wrote:
[...]
>>   # Common support
>> -obj-y := sram.o dma.o fb.o counter_32k.o
>> +obj-y := sram.o dma.o fb.o
>>   obj-m :=
>>   obj-n :=
>>   obj-  :=
>>
>> +obj-$(CONFIG_OMAP_32K_TIMER) += counter_32k.o
>
> We are moving away from this config option in favor of runtime detection,

Well, I'll be happy when it'll happen.

> Why do you need this?

Because until now the build system doesn't honour the config file. 
Indeed it builds that source code file also when I set 
CONFIG_OMAP_32K_TIMER to n.

The runtime detection isn't a good excuse for doesn't make the build 
system working like users expect.

Ciao,
Alessio
--
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/