From: Andi Kleen <ak@suse.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH/RFC] arch/x86_common: more formal reuse of i386+x86_64 source code
Date: Thu, 9 Feb 2006 10:59:40 +0100 [thread overview]
Message-ID: <200602091059.40319.ak@suse.de> (raw)
In-Reply-To: <20060208225336.23539710.rdunlap@xenotime.net>
On Thursday 09 February 2006 07:53, Randy.Dunlap wrote:
> (not completed yet)
> (patch applies to 2.6.16-rc2)
>
> Patch is 331 KB and is at
> http://www.xenotime.net/linux/patches/x86-common1.patch
>
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Move lots of i386 & x86_64 common code into arch/x86_common/
> and modify Makefiles to use it from there.
No. That patch doesn't buy us anything and makes it hell
to forward/backward port patches.
-Andi
next prev parent reply other threads:[~2006-02-09 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:53 [PATCH/RFC] arch/x86_common: more formal reuse of i386+x86_64 source code Randy.Dunlap
2006-02-09 7:00 ` Randy.Dunlap
2006-02-09 9:59 ` Andi Kleen [this message]
2006-02-14 19:22 ` Pavel Machek
2006-02-22 20:53 ` Tom Rini
2006-02-22 20:55 ` Randy.Dunlap
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=200602091059.40319.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).