From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL] usb: build fixes.
Date: Mon, 9 May 2011 14:11:03 +0200 [thread overview]
Message-ID: <1304943065-12023-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Two build issues slipped through with the last usb patch queue pull.
Looks like I should do test builds with a more recent gcc ...
Here are the fixes.
pleae pull,
Gerd
The following changes since commit 85097db6956bc86e2377b63a8309cb8b24d54139:
irq: Privatize CPU_INTERRUPT_NMI. (2011-05-08 16:55:24 +0000)
are available in the git repository at:
git://git.kraxel.org/qemu usb.8.pull
Gerd Hoffmann (1):
usb-musb: uninline functions
Stefan Weil (1):
usb-linux: Add missing break statement
hw/usb-musb.c | 8 ++++----
usb-linux.c | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
next reply other threads:[~2011-05-09 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 12:11 Gerd Hoffmann [this message]
2011-05-09 12:11 ` [Qemu-devel] [PATCH 1/2] usb-musb: uninline functions Gerd Hoffmann
2011-05-09 12:11 ` [Qemu-devel] [PATCH 2/2] usb-linux: Add missing break statement Gerd Hoffmann
2011-05-09 12:50 ` [Qemu-devel] [PULL] usb: build fixes Peter Maydell
2011-05-09 14:25 ` Gerd Hoffmann
2011-05-09 17:41 ` Anthony Liguori
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=1304943065-12023-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--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).