linux-kernel - Re: 5ada28bf76752 causes compilation error if !CONFIG_LEDS

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:	Tue, 23 Nov 2010 10:59:17 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Berg, Johannes" <johannes.berg@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Hannemann <arnd@...dnet.de>,
	Michal Hocko <mhocko@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>,
	Richard Purdie <rpurdie@...ux.intel.com>
Subject: Re: 5ada28bf76752 causes compilation error if !CONFIG_LEDS_CLASS


* Berg, Johannes <johannes.berg@...el.com> wrote:

> > It fails to build on x86 64-bit allmodconfig:
> > 
> > drivers/leds/led-triggers.c:39:20: error: ‘TRIG_NAME_MAX’ undeclared
> > (first use in this function)
> 
> Grr. I give up on the modular thing ...
> 
> There are a whole bunch of ifdefs on TRIGGERS, which need to be
> || modular, but the easier thing is to remove the bool->tristate
> changes from my patch.

Please post a patch that does so.

Thanks,

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