From: Jeff Dike <jdike@addtoit.com>
To: Andi Kleen <ak@suse.de>
Cc: Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
Kyle Moffett <mrmacman_g4@mac.com>
Subject: Re: [uml-devel] [PATCH 1/2] Split i386 and x86_64 ptrace.h
Date: Tue, 8 Aug 2006 22:09:35 -0400 [thread overview]
Message-ID: <20060809020935.GB8201@ccure.user-mode-linux.org> (raw)
In-Reply-To: <p73u04mol9k.fsf@verdi.suse.de>
On Wed, Aug 09, 2006 at 01:33:43AM +0200, Andi Kleen wrote:
> I think I would prefer a well placed ifdef __KERNEL__ or two for this - i don't
> like it when it becomes harder to grep include files like this
> (like the errno->errno-base split was quite bad in this regard)
__KERNEL__ doesn't help because UML defines it just like any other arch.
If you want to play ifdef tricks, it would have to be #ifdef UML, or something
similar.
Jeff
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-08-09 2:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 20:58 [uml-devel] [PATCH 1/2] Split i386 and x86_64 ptrace.h Jeff Dike
2006-08-08 23:33 ` Andi Kleen
2006-08-09 2:09 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 15:52 Jeff Dike
2006-09-13 12:57 ` David Woodhouse
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=20060809020935.GB8201@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.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