From: Jocelyn Mayer <l_indien@magic.fr>
To: thayne@c2.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target_posix_types.h
Date: Wed, 14 Nov 2007 17:25:46 +0100 [thread overview]
Message-ID: <1195057546.21958.56.camel@jma4.dev.netgem.com> (raw)
In-Reply-To: <1195055987.918.34.camel@phantasm.home.enterpriseandprosperity.com>
On Wed, 2007-11-14 at 08:59 -0700, Thayne Harbaugh wrote:
> This patch, 44_target_posix_types.patch provides target specific posix
> types. These types improve target structure creation, code similarity
> to kernel code and improve type casting for assignment between target
> and host.
Hi,
This seems not OK for ppc/ppc64. There is no ppc64 subdirectory anymore
in the linux-user directory. ppc and ppc64 targets have been merged, as
it is in recent kernels, so all the definitions should go in the ppc
subdirectory, using #ifdef TARGET_PPC64 when there are differences; but
there should be very few: there are only 2 ifdef __powerpc64__ in the
linux-2.6.23/include/asm-powerpc/posix_types.h file.
--
Jocelyn Mayer <l_indien@magic.fr>
next prev parent reply other threads:[~2007-11-14 16:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 15:59 [Qemu-devel] [PATCH] target_posix_types.h Thayne Harbaugh
2007-11-14 16:03 ` [Qemu-devel] Re: [PATCH] tget/tput deprecation Thayne Harbaugh
2007-11-14 16:08 ` Thayne Harbaugh
2007-11-14 18:21 ` Thayne Harbaugh
2007-11-14 19:02 ` Thayne Harbaugh
2007-11-16 4:16 ` Thayne Harbaugh
2007-11-14 16:25 ` Jocelyn Mayer [this message]
2007-11-14 17:36 ` [Qemu-devel] [PATCH] target_posix_types.h Thiemo Seufer
2007-11-14 17:54 ` Jocelyn Mayer
2007-11-14 18:20 ` Thayne Harbaugh
2007-11-14 18:32 ` Fabrice Bellard
2007-11-14 18:43 ` Thayne Harbaugh
2007-11-14 19:14 ` Fabrice Bellard
2007-11-14 19:53 ` Thayne Harbaugh
2007-11-14 20:39 ` Paul Brook
2007-11-14 21:06 ` Warner Losh
2007-11-14 21:25 ` Thayne Harbaugh
2007-11-14 21:19 ` Thayne Harbaugh
2007-11-14 21:37 ` Paul Brook
2007-11-14 19:56 ` Thayne Harbaugh
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=1195057546.21958.56.camel@jma4.dev.netgem.com \
--to=l_indien@magic.fr \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.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).