From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/1] Usb 20190607 patches
Date: Fri, 7 Jun 2019 18:56:49 +0200 [thread overview]
Message-ID: <20190607165650.8801-1-kraxel@redhat.com> (raw)
The following changes since commit 442bac16a6cd708a9f87adb0a263f9d833f03ed5:
usb-tablet: fix serial compat property (2019-05-29 07:10:02 +0200)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/usb-20190607-pull-request
for you to fetch changes up to e39b8a66d2af913e873256aa77ea71a179dfe5e0:
usb-mtp: refactor the flow of usb_mtp_write_data (2019-06-07 18:56:14 +0200)
----------------------------------------------------------------
usb-mtp: refactor the flow of usb_mtp_write_data
----------------------------------------------------------------
Bandan Das (1):
usb-mtp: refactor the flow of usb_mtp_write_data
hw/usb/dev-mtp.c | 57 +++++++++++++++++++++++++-----------------------
1 file changed, 30 insertions(+), 27 deletions(-)
--
2.18.1
next reply other threads:[~2019-06-07 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 16:56 Gerd Hoffmann [this message]
2019-06-07 16:56 ` [Qemu-devel] [PULL 1/1] usb-mtp: refactor the flow of usb_mtp_write_data Gerd Hoffmann
2019-06-10 11:55 ` [Qemu-devel] [PULL 0/1] Usb 20190607 patches Peter Maydell
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=20190607165650.8801-1-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).