From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Chris Wright <chrisw@sous-sol.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Announce] Unified x86 architecture, arch/x86 - V2
Date: Wed, 22 Aug 2007 19:09:51 -0400 [thread overview]
Message-ID: <20070822230951.GI17546@redhat.com> (raw)
In-Reply-To: <1187819782.3316.8.camel@chaos>
On Wed, Aug 22, 2007 at 11:56:22PM +0200, Thomas Gleixner wrote:
> We are pleased to announce v2 of the unified arch/x86 project we are
> working on.
>
> To recap: the core idea behind our project is simple to describe: we
> introduce a new arch/x86/ and include/asm-x86/ file hierarchy that
> includes all the existing 32-bit and 64-bit x86 code and allows the
> building of either a 32-bit (i386) kernel or a 64-bit (x86_64) kernel.
> No code is lost and almost no code is modified. We want the window
> for regressions and tree incompatibilities to be zero. (The full initial
> announcement can be found at http://lkml.org/lkml/2007/7/20/447)
>
> The main technical request for improvement we received was the lack of a
> patch-series, and this v2 release does that, in form of a 600+ commits
> git tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git
Nice work. cpufreq bits look sane from a quick eyeball.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-08-22 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 21:56 [Announce] Unified x86 architecture, arch/x86 - V2 Thomas Gleixner
2007-08-22 23:09 ` Dave Jones [this message]
2007-08-23 7:43 ` Muli Ben-Yehuda
2007-08-23 15:51 ` Arjan van de Ven
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=20070822230951.GI17546@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.