From: David Matlack <dmatlack@google.com>
To: Alex Williamson <alex@shazbot.org>
Cc: Josh Hilke <jrhilke@google.com>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Vipin Sharma <vipinsh@google.com>,
Alex Williamson <alex.williamson@nvidia.com>
Subject: Re: [PATCH v10 0/3] vfio: selftests: Add driver for Intel Ethernet Gigabit Controller (IGB)
Date: Fri, 7 Aug 2026 22:27:56 +0000 [thread overview]
Message-ID: <anZb7DlyLSMgp6sK@google.com> (raw)
In-Reply-To: <20260805094621.665d5ec0@shazbot.org>
On 2026-08-05 09:46 AM, Alex Williamson wrote:
> On Wed, 05 Aug 2026 00:20:57 +0000
> Josh Hilke <jrhilke@google.com> wrote:
>
> > This v10 of a series which adds a VFIO selftest driver for the Intel
> > Gigabit Ethernet controller (IGB), specifically targeting the 82576
> > device. IGB is fully virtualized in QEMU, making it suitable for running
> > VFIO selftests without specialized hardware.
>
> LGTM, passes on physical NIC. Thanks for the re-spins.
>
> David, do you want to double check and provide an Ack? Thanks,
>
> Alex
Acked-by: David Matlack <dmatlack@google.com>
next prev parent reply other threads:[~2026-08-07 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 0:20 [PATCH v10 0/3] vfio: selftests: Add driver for Intel Ethernet Gigabit Controller (IGB) Josh Hilke
2026-08-05 0:20 ` [PATCH v10 1/3] vfio: selftests: Add helpers to re-enable interrupts Josh Hilke
2026-08-05 0:20 ` [PATCH v10 2/3] vfio: selftests: igb: Add driver for Intel 82576 device Josh Hilke
2026-08-05 0:21 ` [PATCH v10 3/3] vfio: selftests: Retry on EAGAIN during device reset Josh Hilke
2026-08-05 15:46 ` [PATCH v10 0/3] vfio: selftests: Add driver for Intel Ethernet Gigabit Controller (IGB) Alex Williamson
2026-08-07 22:27 ` David Matlack [this message]
2026-08-10 23:40 ` Alex Williamson
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=anZb7DlyLSMgp6sK@google.com \
--to=dmatlack@google.com \
--cc=alex.williamson@nvidia.com \
--cc=alex@shazbot.org \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=vipinsh@google.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 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).