From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5954] linux-user: Move abi_* typedefs into qemu-types.h
Date: Fri, 12 Dec 2008 23:18:30 +0000 [thread overview]
Message-ID: <20081212231830.GA9457@miranda.arrow> (raw)
In-Reply-To: <639EF387-AF5D-4344-A09C-63403DAD8AAD@web.de>
On Fri, Dec 12, 2008 at 11:57:02PM +0100, Andreas Färber wrote:
> Am 12.12.2008 um 23:40 schrieb Stuart Brady:
> >Sorry if I'm a little late with this comment, but might it be better
> >if bsd-user and linux-user emulation shared the same header, here?
>
> Fabrice was said to be against sharing code between the various user
> emulators.
Hmm, good point -- but these definitions seem so fundamental that I
wonder whether that still applies. I.e. should each user emulator have
its own definitions of target_long, etc. too? (Well, obviously not...)
--
Stuart Brady
prev parent reply other threads:[~2008-12-12 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 18:12 [Qemu-devel] [5954] linux-user: Move abi_* typedefs into qemu-types.h Aurelien Jarno
2008-12-12 22:40 ` Stuart Brady
2008-12-12 22:57 ` Andreas Färber
2008-12-12 23:18 ` Stuart Brady [this message]
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=20081212231830.GA9457@miranda.arrow \
--to=sdbrady@ntlworld.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).