From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL for usb-next]: Move usb-redir over to using more usb-core infra + misc ehci fixes
Date: Tue, 04 Sep 2012 12:05:04 +0200 [thread overview]
Message-ID: <5045D250.3060902@redhat.com> (raw)
In-Reply-To: <5045CA85.20807@redhat.com>
Hi,
> Fulfilling your request would mean wrapping 90% of all function
> prototypes in hw/usb/redirect.c with #ifdef magic. Which I find rather
> ugly. If you prefer the ifdef's over the hard version requirement,
> I can do the ifdef-s, but my preference is to just put the hard
> version dependency on the latest usbredir in there.
Ok, too much trouble, lets skip it then. We'll do it just after the 1.2
release so there is time for people to adapt before 1.3 gets released.
Applied patches, fixed up codestyle, reordered to group patches, pushed
to usb-next.
cheers,
Gerd
prev parent reply other threads:[~2012-09-04 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 14:02 [Qemu-devel] [PULL for usb-next]: Move usb-redir over to using more usb-core infra + misc ehci fixes Hans de Goede
2012-09-04 8:36 ` Gerd Hoffmann
2012-09-04 9:31 ` Hans de Goede
2012-09-04 10:05 ` Gerd Hoffmann [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=5045D250.3060902@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).