From: Chris Wright <chrisw@sous-sol.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
Glauber de Oliveira Costa <glommer@gmail.com>
Subject: Re: [RFC/PATCH 00/59] Make common x86 arch area for i386 and x86_64
Date: Tue, 13 Mar 2007 14:45:12 -0700 [thread overview]
Message-ID: <20070313214512.GM10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <1173820919.28042.3.camel@localhost.localdomain>
* Steven Rostedt (rostedt@goodmis.org) wrote:
> Recently I've been doing some work that will affect both the i386 and x86_64
> architectures. So there will be common code for both, as well as code
> that will be unique for the specific arch. So I was looking into a way
> to do this cleanly, and found that there is no clean way to share code
> between x86_64 and i386.
Thanks for taking this on. I'm sure Andi has a bunch of ideas on this
topic, but it would be nice to see the consolidation.
> So the move patches are a simple move of one file, with the slight exception
> of files that hold the speedstep-lib.h file. This file was moved from the
> arch/i386/kerne/cpu/cpufreq directory and put into the include/asm-i386
> directory. This was due to the fact that some of the moved files included
> it, and some files that were not moved also included it. Instead of using
> the #include "../../x86/" hack again, I just simply moved it to the global
> i386 include directory. Only the arch/x86 will use the include/asm-i386
what about asm-x86/ dir? the asm/ symlink would still point to relevant
arch, but the file there could be simply #include <asm-x86/file.h> ?
thanks,
-chris
next prev parent reply other threads:[~2007-03-13 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1173820919.28042.3.camel@localhost.localdomain>
2007-03-13 21:39 ` Linus Torvalds
2007-03-14 1:02 ` Steven Rostedt
2007-03-14 10:12 ` Andi Kleen
2007-03-14 22:05 ` Rusty Russell
2007-03-14 12:49 ` Ingo Molnar
2007-03-13 21:45 ` Chris Wright [this message]
2007-03-14 1:05 ` Steven Rostedt
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=20070313214512.GM10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=ak@muc.de \
--cc=akpm@linux-foundation.org \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®