All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Herrmann" <andreas.herrmann3@amd.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"LKML" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: unification of cfufreq/Kconfig
Date: Fri, 9 Nov 2007 19:36:02 +0100	[thread overview]
Message-ID: <20071109183602.GD1988@alberich.amd.com> (raw)
In-Reply-To: <20071106230451.GA10886@uranus.ravnborg.org>

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




  parent reply	other threads:[~2007-11-09 18:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06 23:01 [PATCH] x86: unification of cfufreq/Kconfig Sam Ravnborg
2007-11-06 23:01 ` [PATCH] x86: start unification of arch/x86/Kconfig.* Sam Ravnborg
2007-11-06 23:01   ` [PATCH] x86: arch/x86/Kconfig.cpu unification Sam Ravnborg
2007-11-06 23:01     ` [PATCH] x86: add X86_32 dependency to i386 specific symbols in Kconfig.i386 Sam Ravnborg
2007-11-06 23:01       ` [PATCH] x86: add X86_64 dependency to x86_64 specific symbols in Kconfig.x86_64 Sam Ravnborg
2007-11-06 23:01         ` [PATCH] x86: copy x86_64 specific Kconfig symbols to Kconifg.i386 Sam Ravnborg
2007-11-06 23:01           ` [PATCH] x86: move all simple arch settings to Kconfig Sam Ravnborg
2007-11-06 23:01             ` [PATCH] x86: move the rest of the menu's " Sam Ravnborg
2007-11-06 23:04 ` [PATCH] x86: unification of cfufreq/Kconfig Sam Ravnborg
2007-11-07  5:46   ` Sam Ravnborg
2007-11-09 18:36   ` Andreas Herrmann [this message]
2007-11-09 18:45     ` Thomas Gleixner
2007-11-09 19:41       ` Sam Ravnborg
2007-11-09 19:42     ` Sam Ravnborg
2007-11-12 10:45     ` Adrian Bunk
2007-11-07  6:02 ` Adrian Bunk
2007-11-07  7:06   ` Sam Ravnborg
2007-11-07  7:18     ` Adrian Bunk
2007-11-07 16:06       ` Sam Ravnborg
2007-11-08 14:51         ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2007-11-12 20:54 [PATCH revised] enable make ARCH=x86 (and stay backward compatible) Sam Ravnborg
2007-11-12 21:00 ` [PATCH] x86: unification of cfufreq/Kconfig Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071109183602.GD1988@alberich.amd.com \
    --to=andreas.herrmann3@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.