linux-kernel - Re: sparc64 allmodconfig build failure...

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, 14 Oct 2008 15:49:16 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	sven.wegener@...aler.net
Cc:	adobriyan@...il.com, davej@...hat.com,
	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org
Subject: Re: sparc64 allmodconfig build failure...

From: Sven Wegener <sven.wegener@...aler.net>
Date: Tue, 14 Oct 2008 23:08:17 +0200 (CEST)

> Yeah, with the default governor being any of supported governors, we
> either need some ugly #ifdef mess to only export the governor that
> is selected or just revert to the old code, which unconditionally
> exports all governors. Or something like the patch below. With the
> additional modules that I oversaw and that require the export, I'm
> fine with just reverting the commit, although I think that
> encapsulating the default governor decision in a built-in function
> is cleaner than having modules reference different symbols depending
> on configuration.

Personally I prefer the revert.

All of the alternative solutions shown far have been extremely
ugly.
--
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/