From: "Andreas Färber" <afaerber@suse.de>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_s390
Date: Thu, 15 Mar 2012 10:16:22 +0100 [thread overview]
Message-ID: <4F61B366.30708@suse.de> (raw)
In-Reply-To: <0DE7FD9D-EDA2-4AD8-875A-0FA65798BCDE@suse.de>
Am 15.03.2012 09:32, schrieb Alexander Graf:
>
> On 15.03.2012, at 01:11, Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
>
>> On Thu, Mar 15, 2012 at 01:01:04AM +0100, Andreas Färber wrote:
>>> My GCC handles the following code fine:
>>>
>>> typedef struct CPULM32State CPULM32State;
>>>
>>> typedef struct CPULM32State {
>>> // ...
>>> } CPULM32State;
>>>
>>> Solutions would be to
>>> a) drop the second typedef,
>>> b) use struct CPULM32State,
>>> c) move the function using it to after the second typedef.
>>
>> I vote for a)
>
> Same here.
Long fixed. :) Wait, you haven't actually been sleeping at night this
once? ;)
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-15 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 0:16 [Qemu-devel] buildbot failure in qemu on default_s390 qemu
2012-03-15 0:01 ` Andreas Färber
2012-03-15 0:11 ` Michael Roth
2012-03-15 8:32 ` Alexander Graf
2012-03-15 9:16 ` Andreas Färber [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-14 23:57 qemu
2012-03-25 0:03 qemu
2012-01-24 0:09 qemu
2011-10-26 9:16 qemu
2011-10-30 16:42 ` Alexander Graf
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=4F61B366.30708@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--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).