[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071109183602.GD1988@alberich.amd.com>
Date: Fri, 9 Nov 2007 19:36:02 +0100
From: "Andreas Herrmann" <andreas.herrmann3@....com>
To: "Sam Ravnborg" <sam@...nborg.org>
cc: "Thomas Gleixner" <tglx@...utronix.de>,
"Ingo Molnar" <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: unification of cfufreq/Kconfig
On Wed, Nov 07, 2007 at 12:04:51AM +0100, Sam Ravnborg wrote:
> This serie of patches unify the X86 Kconfig files.
> Next step is to enable use of "make ARCH=x86" and kill
> "make ARCH=i386/x86_64".
> But that will wait till tomorrow.
>
> The allmodconfig kernel is still building here.
> Testing / reviews appreciated.
>
> Comments from former patchset is addressed - see
> changelog entries.
Just some kind of feedback wrt your patch set.
I did several hundred randconfig kernel compiles based
on 2.6.24-rc2 with your patches on top plus those additional
minor fixes mentioned on lkml.
>From what I've seen there were no compile failures that seem
to be caused by your adaptations.
Mostly I have seen the ususal suspects (e.g. missing firmware and
lots of failed configs due to conflicting types for net_free
- AFAIK that is already solved in netdev tree - and due to the
"kvm-smp_call_function-issue").
The rest (5 failed configs) was not specific to x86 but driver
related (e.g. v4l).
Regards,
Andreas
PS: Looking forward to test the ARCH=x86 enabled kbuild.
BTW, what is the right git tree to pull this stuff from?
Is it your x86.git tree? But that one is not up to date, is it?
--
Operating | AMD Saxony Limited Liability Company & Co. KG,
System | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Research | Register Court Dresden: HRA 4896, General Partner authorized
Center | to represent: AMD Saxony LLC (Wilmington, Delaware, US)
(OSRC) | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
-
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/
Powered by blists - more mailing lists