qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: "Andreas Färber" <andreas.faerber@web.de>,
	"Alexander Graf" <agraf@suse.de>,
	"QEMU-devel Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] USB: Fix build breakage in musb
Date: Mon, 09 May 2011 09:43:09 +0200	[thread overview]
Message-ID: <4DC79B0D.1040603@redhat.com> (raw)
In-Reply-To: <4DC6BFE3.7020204@mail.berlios.de>

   Hi,

> Looking closer at file hw/usb-musb.c, I'd even recommend removing
> all 'inline' attributes there:

I'll do that.

/me wonders why the local test build worked just fine.  Seems recent gcc 
versions became pickier (running gcc 4.4).

cheers,
   Gerd

  reply	other threads:[~2011-05-09  7:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07 22:59 [Qemu-devel] [PATCH] USB: Fix build breakage in musb Alexander Graf
2011-05-08 15:40 ` Andreas Färber
2011-05-08 15:54 ` Stefan Weil
2011-05-08 16:08   ` Stefan Weil
2011-05-09  7:43     ` Gerd Hoffmann [this message]
2011-05-09  9:05       ` 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=4DC79B0D.1040603@redhat.com \
    --to=kraxel@redhat.com \
    --cc=agraf@suse.de \
    --cc=andreas.faerber@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).