From: Stephen Hemminger <stephen@networkplumber.org>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
Yongji Xie <xieyongji@bytedance.com>,
mst@redhat.com, jasowangio@gmail.com,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, chenbox@nvidia.com, david.marchand@redhat.com
Subject: Re: [PATCH v4 1/9] uapi: import VDUSE and VFIO header from v7.3-rc7 kernel
Date: Wed, 14 Oct 2026 10:16:47 -0700 [thread overview]
Message-ID: <20261014101647.1164eca0@phoenix.local> (raw)
In-Reply-To: <20261014082930.96261-2-eperezma@redhat.com>
On Wed, 14 Oct 2026 10:29:22 +0200
Eugenio Pérez <eperezma@redhat.com> wrote:
> This header will be used by the Vhost library.
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Please only use uapi headers from released kernels.
next prev parent reply other threads:[~2026-10-14 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:29 [PATCH v4 0/9] Add vduse live migration features Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 1/9] uapi: import VDUSE and VFIO header from v7.3-rc7 kernel Eugenio Pérez
2026-10-14 17:16 ` Stephen Hemminger [this message]
2026-10-14 8:29 ` [PATCH v4 2/9] vhost: introduce ASID support Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 3/9] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 4/9] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 5/9] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 6/9] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 7/9] vhost: add net status feature to VDUSE Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 8/9] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-10-14 8:29 ` [PATCH v4 9/9] vhost: Support vduse suspend feature Eugenio Pérez
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=20261014101647.1164eca0@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=xieyongji@bytedance.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