From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c question
Date: Fri, 8 Jul 2005 00:08:45 +0100 [thread overview]
Message-ID: <b4fee4415ac8f189608cc1b7971c27c1@terzarima.net> (raw)
In-Reply-To: <310D4BA6-03CF-43D6-8E1D-7B5F312E85F7@gmail.com>
i don't understand. if it's in the portability interface,
you say what arch_vcpu_info_t is, so why not
typedef int arch_vcpu_info_t;
and be done with it. i don't see why it must be a struct
in that context.
i'd assumed (based on having looked at some xen headers
a month ago) that they'd used 0-length things to try to
get round some portability problem with `packed' structs,
but the problem seems simpler than that.
next prev parent reply other threads:[~2005-07-07 23:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 23:17 Tim Newsham
2005-07-02 12:43 ` Charles Forsyth
2005-07-05 2:36 ` David Leimbach
2005-07-05 14:47 ` Ronald G. Minnich
2005-07-05 15:27 ` Latchesar Ionkov
2005-07-05 15:33 ` Ronald G. Minnich
2005-07-05 18:33 ` Tim Newsham
2005-07-05 15:35 ` David Leimbach
2005-07-07 23:08 ` Charles Forsyth [this message]
2005-07-08 0:06 ` Ronald G. Minnich
2005-07-08 0:27 ` Russ Cox
2005-07-08 14:36 ` Ronald G. Minnich
2005-07-08 19:03 ` jmk
2005-07-08 19:40 ` Charles Forsyth
2005-07-09 1:02 ` Ronald G. Minnich
2005-07-08 3:31 ` Tim Newsham
2005-07-08 11:14 ` Charles Forsyth
2005-07-09 1:04 ` Tim Newsham
2005-07-09 9:40 ` Charles Forsyth
2005-07-11 0:57 ` Ronald G. Minnich
2005-07-11 1:26 ` [9fans] Xen comms Tim Newsham
2005-07-11 19:21 ` Eric Van Hensbergen
2005-07-11 19:23 ` [9fans] 8c question Eric Van Hensbergen
2005-07-11 19:58 ` Ronald G. Minnich
2005-07-11 20:05 ` Eric Van Hensbergen
2005-07-11 20:15 ` Ronald G. Minnich
2005-07-11 20:35 ` Eric Van Hensbergen
2005-07-11 20:38 ` Ronald G. Minnich
2005-07-11 21:03 ` Eric Van Hensbergen
2005-07-11 21:09 ` Ronald G. Minnich
2005-07-11 21:13 ` Eric Van Hensbergen
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=b4fee4415ac8f189608cc1b7971c27c1@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).