From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] Re: [Xen-staging] [xen-unstable] Explicitly tag every anonymous aggregate in the public headers.
Date: Fri, 28 Mar 2008 16:55:53 -0600 [thread overview]
Message-ID: <1206744953.7320.68.camel@lappy> (raw)
In-Reply-To: <C41323A9.15866%keir.fraser@eu.citrix.com>
On Fri, 2008-03-28 at 22:37 +0000, Keir Fraser wrote:
> On 28/3/08 21:04, "Alex Williamson" <alex.williamson@hp.com> wrote:
>
> > @@ -609,7 +609,7 @@ struct xen_ia64_opt_feature {
> > unsigned long cmd; /* Which feature */
> > unsigned char on; /* Switch feature on/off */
> > __anonymous_union {
> > - __anonymous_struct {
> > + struct {
> > /* The page protection bit mask of the pte.
> > * This will be or'ed with the pte. */
> > unsigned long pgprot;
>
> I have no idea if it's the cause of this particular boot breakage, but I
> reckon that an anonymous union containing a single anonymous struct can be
> simplified. Or perhaps, if the union is there for stylistic reasons, a
> single extra field in the union would fix things?
I toggled this one separately exactly for that reason, but it's not
the one. I still haven't isolated a particular reason why it fails in a
test program, but I'll keep trying. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
prev parent reply other threads:[~2008-03-28 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803261016.m2QAGPsq017512@latara.uk.xensource.com>
2008-03-26 15:11 ` [PATCH] Re: [Xen-staging] [xen-unstable] Explicitly tag every anonymous aggregate in the public headers Alex Williamson
2008-03-27 14:37 ` Alex Williamson
2008-03-28 21:04 ` Alex Williamson
2008-03-28 21:47 ` Keir Fraser
2008-03-31 15:49 ` Alex Williamson
2008-03-31 16:21 ` Keir Fraser
2008-03-31 16:28 ` Alex Williamson
2008-03-28 22:37 ` Keir Fraser
2008-03-28 22:55 ` Alex Williamson [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=1206744953.7320.68.camel@lappy \
--to=alex.williamson@hp.com \
--cc=keir.fraser@eu.citrix.com \
--cc=samuel.thibault@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.