linux-kernel - Re: [git pull] x86 fixes

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, 5 May 2008 18:12:02 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andres Salomon <dilinger@...ian.org>
Subject: Re: [git pull] x86 fixes

On Sun, May 04, 2008 at 09:35:42PM +0200, Ingo Molnar wrote:
>...
> Thomas Gleixner (2):
>...
>       x86: olpc build fix
>...
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1661,6 +1661,7 @@ config GEODE_MFGPT_TIMER
>  
>  config OLPC
>  	bool "One Laptop Per Child support"
> +	depends on MGEODE_LX
>  	default n
>  	help
>...

This patch not only excludes OLPC and code depending on it (currently 
BATTERY_OLPC) from all{mod,yes}config builds (where it built fine) 
but also makes it very hard for generic distribution kernels to
support the OLPC.

The commit comment does not indicate what the actual problem was, and if 
this patch was sent to linux-kernel I must have missed it.

What exactly was the build problem?
Can we fix it in a less invasive way?

Thanks in advance
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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