All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junjie Cao <junjie.cao@linux.dev>
To: thuth@redhat.com
Cc: peter.maydell@linaro.org, farosas@suse.de, lvivier@redhat.com,
	pbonzini@redhat.com, philmd@oss.qualcomm.com,
	qemu-devel@nongnu.org, junjie.cao@intel.com
Subject: Re: [PATCH] tests/qtest: Cover OHCI endpoint type mismatches
Date: Sat, 17 Oct 2026 06:21:48 +0000	[thread overview]
Message-ID: <20261017062148.610962-1-junjie.cao@linux.dev> (raw)
In-Reply-To: <c5fab461-2645-489e-ba72-5ee7b51a2507@redhat.com>

Thanks for the review, Thomas. I've merged the duplicate checks and
moved expected[] as suggested.

v2 also removes the x86 restriction, with little-endian DMA accesses
and PCI host bridge IOMMU bypass. The tests pass on aarch64 and
ppc64 as well as x86.

Junjie


      reply	other threads:[~2026-10-17  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  9:30 [PATCH] tests/qtest: Cover OHCI endpoint type mismatches Junjie Cao
2026-10-16 11:47 ` Thomas Huth
2026-10-17  6:21   ` Junjie Cao [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=20261017062148.610962-1-junjie.cao@linux.dev \
    --to=junjie.cao@linux.dev \
    --cc=farosas@suse.de \
    --cc=junjie.cao@intel.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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.