From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] usb/host-libusb: Fix building with libusb git master code
Date: Thu, 06 Jun 2013 16:47:43 +0200 [thread overview]
Message-ID: <51B0A10F.6030406@redhat.com> (raw)
In-Reply-To: <1370529574-31069-3-git-send-email-hdegoede@redhat.com>
On 06/06/13 16:39, Hans de Goede wrote:
> The next libusb release will deprecate libusb_get_port_path, and since
> we compile with -Werror, this breaks the build.
Patch added to usb patch queue.
thanks,
Gerd
next prev parent reply other threads:[~2013-06-06 14:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 14:39 [Qemu-devel] [PATCH 0/2] 2 compile / build fixes Hans de Goede
2013-06-06 14:39 ` [Qemu-devel] [PATCH 1/2] device_tree: Fix build with latest libfdt Hans de Goede
2013-06-06 14:51 ` Gerd Hoffmann
2013-06-11 2:13 ` Peter Crosthwaite
2013-06-12 13:55 ` Paolo Bonzini
2013-06-12 14:01 ` Peter Maydell
2013-06-12 14:03 ` Paolo Bonzini
2013-06-06 14:39 ` [Qemu-devel] [PATCH 2/2] usb/host-libusb: Fix building with libusb git master code Hans de Goede
2013-06-06 14:47 ` Gerd Hoffmann [this message]
2013-06-07 14:13 ` Ed Maste
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=51B0A10F.6030406@redhat.com \
--to=kraxel@redhat.com \
--cc=hdegoede@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).