linux-kernel - Re: [PATCH -next] x86 mrst: fix build error when X86

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]

Message-ID: <20110930100404.1a83ce65@lxorguk.ukuu.org.uk>
Date:	Fri, 30 Sep 2011 10:04:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -next] x86 mrst: fix build error when X86_MRST is not
 enabled

> arch/x86/platform/mrst/mrst.c -- where __mrst_cpu_chip lives --

In your tree yes

> is only built when CONFIG_X86_MRST is enabled.  You make it sound like
> __mrst_cpu_chip needs to live any time that CONFIG_X86_INTEL_MID
> is enabled, which sounds reasonable to me.
> 
> caveat:  given the current linux-next merge trees (as you mentioned).
> 
> Does anyone care?  If so, please help fix this muck.

It's already sorted, you are just seeing an out of order arrival of
patches to trees. I guess once kernel.org is back it'll all sort

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