From: "H. Peter Anvin" <hpa@zytor.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>, Matt Domsch <Matt_Domsch@dell.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@in.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: x86 setup rewrite tree ready for flamage^W review
Date: Tue, 08 May 2007 22:15:21 -0700 [thread overview]
Message-ID: <464158E9.2000207@zytor.com> (raw)
Hello all,
I believe the x86 setup tree is now finished. I will turn it into a
"clean patchset" later this week, but I wanted to get flamed^W feedback
on it first.
The git tree is at:
http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-newsetup.git;a=summary
git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-newsetup.git
...
... and a flat patch at ...
http://www.kernel.org/pub/linux/kernel/people/hpa/newsetup-36f021b5.patch
-hpa
next reply other threads:[~2007-05-09 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:15 H. Peter Anvin [this message]
2007-05-09 6:51 ` x86 setup rewrite tree ready for flamage^W review Sam Ravnborg
2007-05-09 7:02 ` H. Peter Anvin
2007-05-09 8:11 ` Sam Ravnborg
2007-05-10 14:10 ` Alexander van Heukelum
2007-05-10 18:08 ` H. Peter Anvin
2007-05-10 18:38 ` Martin Mares
2007-05-11 0:55 ` H. Peter Anvin
2007-05-10 22:04 ` Alexander van Heukelum
2007-05-10 22:48 ` H. Peter Anvin
2007-05-12 12:21 ` Alexander van Heukelum
2007-05-12 14:20 ` Eric W. Biederman
2007-05-12 18:09 ` H. Peter Anvin
2007-05-12 18:35 ` Eric W. Biederman
2007-05-12 18:59 ` H. Peter Anvin
2007-05-12 22:04 ` Eric W. Biederman
2007-05-12 22:08 ` H. Peter Anvin
2007-05-11 4:37 ` Vivek Goyal
2007-05-11 23:58 ` Kevin Winchester
2007-05-12 0:23 ` H. Peter Anvin
2007-05-13 0:35 ` Kevin Winchester
2007-05-15 20:45 ` Rob Landley
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=464158E9.2000207@zytor.com \
--to=hpa@zytor.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Matt_Domsch@dell.com \
--cc=adaplas@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/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.