From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Cc: Junjie Cao <junjie.cao@linux.dev>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [PULL 0/5] Misc patches before the v11.2 softfreeze
Date: Mon, 2 Nov 2026 17:30:39 +0100 [thread overview]
Message-ID: <20261102163044.644663-1-thuth@redhat.com> (raw)
Hi Richard!
The following changes since commit 56afd82bd4db9688f1c1c9d0e2ea163b8cde3283:
Merge tag 'qemu-sparc-20261101' of https://github.com/mcayland/qemu into staging (2026-11-01 08:37:48 -0800)
are available in the Git repository at:
https://gitlab.com/thuth/qemu.git tags/pull-request-2026-11-02
for you to fetch changes up to 213c716c58738be9d39488e56e6d6ed25dacd14e:
tests/qtest/usb-hcd-xhci: test Address Device with an unreadable DCBAA (2026-11-02 15:34:15 +0100)
----------------------------------------------------------------
* Add a "check-thorough" test target
* Make sure that the next-cube machine shows a deprecation note
* Reset the open retry count after a successful open in the usb-host code
* Make sure that XHCI code does not ignore failure when reading the DCBAA
Note: I really don't have time to look for USB patches anymore, so after
this pull request, I'll stop helping out here. We really need a
dedicated person acting as a maintainer for the USB code...
----------------------------------------------------------------
Junjie Cao (3):
usb-host: reset the open retry count after a successful open
hw/usb/hcd-xhci: fail Address Device when the DCBAA entry is unreadable
tests/qtest/usb-hcd-xhci: test Address Device with an unreadable DCBAA
Peter Maydell (1):
hw/m68k/next-cube: Show deprecation notice to users
Thomas Huth (1):
tests: Add a target to run all tests in thorough mode
hw/m68k/next-cube.c | 1 +
hw/usb/hcd-xhci.c | 41 ++++++++++++-------
hw/usb/host-libusb.c | 1 +
tests/qtest/usb-hcd-xhci-test.c | 87 +++++++++++++++++++++++++++++++++++------
tests/Makefile.include | 13 ++++--
5 files changed, 114 insertions(+), 29 deletions(-)
next reply other threads:[~2026-11-02 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:30 Thomas Huth [this message]
2026-11-02 16:30 ` [PULL 1/5] tests: Add a target to run all tests in thorough mode Thomas Huth
2026-11-02 16:30 ` [PULL 2/5] hw/m68k/next-cube: Show deprecation notice to users Thomas Huth
2026-11-02 16:30 ` [PULL 3/5] usb-host: reset the open retry count after a successful open Thomas Huth
2026-11-02 16:30 ` [PULL 4/5] hw/usb/hcd-xhci: fail Address Device when the DCBAA entry is unreadable Thomas Huth
2026-11-02 16:30 ` [PULL 5/5] tests/qtest/usb-hcd-xhci: test Address Device with an unreadable DCBAA Thomas Huth
2026-11-03 15:24 ` [PULL 0/5] Misc patches before the v11.2 softfreeze Richard Henderson
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=20261102163044.644663-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=junjie.cao@linux.dev \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.