From: Jeff Garzik <jgarzik@pobox.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>, akpm@osdl.org, ak@suse.de
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [Patch] share i386/x86_64 intel cache descriptors table
Date: Wed, 06 Oct 2004 23:25:14 -0400 [thread overview]
Message-ID: <4164B71A.30105@pobox.com> (raw)
In-Reply-To: <20041006184723.A10900@unix-os.sc.intel.com>
I have often wondered if there is any value to creating arch/x86 and
include/asm-x86 for stuff shared between x86-64 and i386.
All this #include and cross-linking stuff gives me the willys...
Jeff
next prev parent reply other threads:[~2004-10-07 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 1:47 [Patch] share i386/x86_64 intel cache descriptors table Suresh Siddha
2004-10-07 3:25 ` Jeff Garzik [this message]
2004-10-07 5:22 ` Willy Tarreau
2004-10-07 7:25 ` common code between i386 and x86_64 (was Re: [Patch] share i386/x86_64 intel cache descriptors table) Suresh Siddha
2004-10-07 9:50 ` Andi Kleen
2004-10-07 9:54 ` [Patch] share i386/x86_64 intel cache descriptors table Andi Kleen
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=4164B71A.30105@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox