From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>
Subject: Re: memop struct packing, 32/64 bits
Date: Fri, 20 Jan 2012 10:32:14 +0000 [thread overview]
Message-ID: <CB3EF32E.37D38%keir@xen.org> (raw)
In-Reply-To: <4F194C00020000780006DD9C@nat28.tlf.novell.com>
On 20/01/2012 10:12, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> Not used in any public header files.
>>>
>>> One seems to have crept into xen/include/public/arch-x86/hvm/save.h :-(
>>
>> Thanks, I'll get rid of it. It looks like it should have no effect on that
>> struct anyway.
>
> While it indeed looks pointless there, all the hvm/save.h headers are
> supposedly tools interface only anyway, so would generally be free
> to use extensions (and are therefore excluded from the ANSI
> correctness test).
True. But since it is not needed and is the only one in the whole public/
directory, I got rid of it anyway.
-- Keir
prev parent reply other threads:[~2012-01-20 10:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 20:30 memop struct packing, 32/64 bits Andres Lagar-Cavilla
2012-01-19 20:49 ` Keir Fraser
2012-01-19 20:57 ` Andres Lagar-Cavilla
2012-01-19 21:11 ` Ian Campbell
2012-01-19 21:21 ` Andres Lagar-Cavilla
2012-01-19 21:23 ` Andres Lagar-Cavilla
2012-01-19 21:56 ` Keir Fraser
2012-01-19 22:00 ` Keir Fraser
2012-01-19 22:04 ` Keir Fraser
2012-01-19 22:05 ` Andres Lagar-Cavilla
2012-01-22 20:37 ` Konrad Rzeszutek Wilk
2012-01-22 20:43 ` Keir Fraser
2012-01-23 9:24 ` Jan Beulich
2012-01-23 15:02 ` Konrad Rzeszutek Wilk
2012-01-19 20:49 ` Konrad Rzeszutek Wilk
2012-01-19 21:07 ` Keir Fraser
2012-01-19 21:12 ` Ian Campbell
2012-01-19 21:56 ` Keir Fraser
2012-01-20 10:12 ` Jan Beulich
2012-01-20 10:32 ` Keir Fraser [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=CB3EF32E.37D38%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andres@lagarcavilla.org \
--cc=konrad@darnok.org \
--cc=xen-devel@lists.xensource.com \
/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).