From: Pavel Machek <pavel@ucw.cz>
To: Andi Kleen <ak@suse.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86
Date: Fri, 27 Jul 2007 10:50:34 +0000 [thread overview]
Message-ID: <20070727105034.GB11895@ucw.cz> (raw)
In-Reply-To: <200707210806.12880.ak@suse.de>
Hi!
> > This patch was the beginning of the merger, not the end result. It strived
> > for binary identical images. It was to put everything together as a
> > _starting_point_! The next thing to do after this is to start the
> > merging.
>
> Well we've been merging what makes sense since several years. So it's not
> really starting anything that hasn't already occurred.
I believe there's still a lot that can be merged, and I'm responsible
for some of it. Parts of suspend code should be shared, yet they are
in differently named files in differently named directories.
Ok, I guess I should fix it, arch/x86 or not.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-07-27 18:08 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
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 [this message]
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=20070727105034.GB11895@ucw.cz \
--to=pavel@ucw.cz \
--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=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 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).