public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH/RFC] x86: unify Kconfig files
Date: Thu, 01 Nov 2007 14:21:30 -0700	[thread overview]
Message-ID: <472A435A.5030508@zytor.com> (raw)
In-Reply-To: <20071101211406.GA7891@uranus.ravnborg.org>

Sam Ravnborg wrote:
> On Wed, Oct 31, 2007 at 10:55:01PM +0100, Sam Ravnborg wrote:
>> It has been requested that we should let x86 behave like
>> other architectures so we at config time decide for 32 or 64 bit.
>> The challenge here is to mere the Kconfig files and I have done
>> an attempt to do so.
> 
> Just a heads up...
> I have started to redo the patch below in smaller chunks and expect
> to finish this tomorrow.
> The cpufreq Kconfig file is done so no need for help here.
> 
> I hope to make the patches small enough so we can be confident to
> apply them despite that we are heading -rc2.
> It would be nice to get "make ARCH=x86" working before next
> kernel release - and with the Kconfig files merged this is trivial.
> I hope the x86 maintainers agree - but that yours decision.
> 

I looked over your patch yesterday and it looked sane to me, but I would 
definitely prefer if it was broken up for reviewability.

	-hpa

      reply	other threads:[~2007-11-01 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 21:55 [PATCH/RFC] x86: unify Kconfig files Sam Ravnborg
2007-11-01  4:08 ` Jeremy Fitzhardinge
2007-11-01  5:25   ` Sam Ravnborg
2007-11-01 21:14 ` Sam Ravnborg
2007-11-01 21:21   ` H. Peter Anvin [this message]

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=472A435A.5030508@zytor.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox