linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Andi Kleen <ak@suse.de>, Arjan van de Ven <arjan@infradead.org>,
	Chris Wright <chrisw@sous-sol.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86
Date: Sat, 21 Jul 2007 02:03:09 +0200	[thread overview]
Message-ID: <20070721000309.GA24829@elte.hu> (raw)
In-Reply-To: <6bffcb0e0707201655q664202e6v29b4e678de1b0d80@mail.gmail.com>


* Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:

> >We are pleased to announce a project we've been working on for some 
> >time: the unified x86 architecture tree, or "arch/x86" - and we'd 
> >like to solicit feedback about it.
> >
> >What is this about?
> [..]
> >As usual, comments and suggestions are welcome!
> 
> I really like this idea - code duplication is a bad thing.
> 
> BTW. I don't see any regression here :)

cool - could you tell us a bit more about on what type of box you tried 
it, and how wide and versatile the .config is?

	Ingo

  reply	other threads:[~2007-07-21  0:03 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 22:32 [RFC, Announce] Unified x86 architecture, arch/x86 Thomas Gleixner
2007-07-20 22:38 ` Jeff Garzik
2007-07-20 22:40   ` Ingo Molnar
2007-07-20 22:42     ` Jeff Garzik
2007-07-20 22:51       ` Linus Torvalds
2007-07-21  2:56     ` Yinghai Lu
2007-07-20 23:55   ` Alan Cox
2007-07-21  0:02     ` H. Peter Anvin
2007-07-21 22:26     ` Oleg Verych
2007-07-20 23:01 ` Arjan van de Ven
2007-07-20 23:23   ` Steven Rostedt
2007-07-21  2:39     ` Glauber de Oliveira Costa
2007-07-20 23:55 ` Michal Piotrowski
2007-07-21  0:03   ` Ingo Molnar [this message]
2007-07-21  0:16     ` Michal Piotrowski
2007-07-21  5:40   ` Andi Kleen
2007-07-21  5:50     ` Steven Rostedt
2007-07-21  6:06       ` Andi Kleen
2007-07-21  7:35         ` Adrian Bunk
2007-07-21  7:42           ` Andi Kleen
2007-07-21  8:01             ` Adrian Bunk
2007-07-21  8:15             ` Thomas Gleixner
2007-07-21  8:32             ` Ingo Molnar
2007-07-27 10:50         ` Pavel Machek
2007-07-27 18:11           ` Chris Wright
2007-07-20 23:55 ` Arnd Bergmann
2007-07-21  1:59   ` Steven Rostedt
2007-07-21  1:01 ` Gabriel C
2007-07-21  5:37 ` Andi Kleen
2007-07-21  5:58   ` Steven Rostedt
2007-07-21  6:09     ` Andi Kleen
2007-07-21  8:15   ` Thomas Gleixner
2007-07-21  8:28     ` Andi Kleen
2007-07-21 13:28       ` Glauber de Oliveira Costa
2007-07-21  9:02     ` Rusty Russell
2007-07-21 11:34     ` Brian Gerst
2007-07-21 12:30       ` Ingo Molnar
2007-07-21 15:11   ` Arjan van de Ven
2007-07-21  6:37 ` Avi Kivity
2007-07-21 10:37 ` David Woodhouse
2007-07-21 10:56 ` Adrian Bunk
2007-07-21 22:25 ` Matt Mackall
2007-07-21 23:51   ` Chris Wright
2007-07-22  7:50     ` Thomas Gleixner
2007-07-22 12:02       ` Matt Mackall

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=20070721000309.GA24829@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.org \
    /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;
as well as URLs for NNTP newsgroup(s).