public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	akpm@osdl.org, ak@suse.de, linux-kernel@vger.kernel.org,
	davej@redhat.com
Subject: common code between i386 and x86_64 (was Re: [Patch] share i386/x86_64 intel cache descriptors table)
Date: Thu, 7 Oct 2004 00:25:50 -0700	[thread overview]
Message-ID: <20041007002550.A12738@unix-os.sc.intel.com> (raw)
In-Reply-To: <4164B71A.30105@pobox.com>; from jgarzik@pobox.com on Wed, Oct 06, 2004 at 11:25:14PM -0400

On Wed, Oct 06, 2004 at 11:25:14PM -0400, Jeff Garzik wrote:
> 
> 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.

Yes. There is definitely some value. Currently this kind of code is scattered
all around the place. With this demarcation, people touching this common
code will be careful of not breaking arch's that are sharing this code.

We can avoid duplicate data structure definitions and duplicate prototypes.

thanks,
suresh

  parent reply	other threads:[~2004-10-07  7:27 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
2004-10-07  5:22   ` Willy Tarreau
2004-10-07  7:25   ` Suresh Siddha [this message]
2004-10-07  9:50     ` common code between i386 and x86_64 (was Re: [Patch] share i386/x86_64 intel cache descriptors table) 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=20041007002550.A12738@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.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