From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com, rppt@kernel.org, ljs@kernel.org,
akpm@linux-foundation.org, virtualization@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tools: Fix tools/virtio test build
Date: Thu, 18 Jun 2026 08:04:19 -0400 [thread overview]
Message-ID: <20260618080405-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <913D9291164C65D4+20260618095642.510565-1-chenyichong@uniontech.com>
On Thu, Jun 18, 2026 at 05:56:40PM +0800, Yichong Chen wrote:
> This series fixes build failures hit by:
>
> make -C tools/virtio test
>
> Patch 1 adds tools/virtio compatibility definitions needed by
> recent virtio headers when building vhost_net_test.
>
> Patch 2 makes tools/include/linux/overflow.h include stdint.h
> for SIZE_MAX, which is used by its size helper functions.
>
> With the series applied, make -C tools/virtio test builds
> virtio_test, vringh_test and vhost_net_test successfully.
>
> Yichong Chen (2):
> tools/virtio: Add missing compat definitions for vhost_net_test
> tools/include: Include stdint.h for SIZE_MAX in overflow.h
which commit is this on top of?
> tools/include/linux/overflow.h | 2 +
> tools/virtio/linux/completion.h | 9 +++++
> tools/virtio/linux/device.h | 1 +
> tools/virtio/linux/dma-mapping.h | 1 +
> tools/virtio/linux/mod_devicetable.h | 14 +++++++
> tools/virtio/linux/slab.h | 4 ++
> tools/virtio/linux/virtio_features.h | 56 ++++++++++++++++++++++++++++
> 7 files changed, 87 insertions(+)
> create mode 100644 tools/virtio/linux/completion.h
> create mode 100644 tools/virtio/linux/mod_devicetable.h
> create mode 100644 tools/virtio/linux/virtio_features.h
>
> --
> 2.51.0
prev parent reply other threads:[~2026-06-18 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 9:56 [PATCH 0/2] tools: Fix tools/virtio test build Yichong Chen
2026-06-18 12:04 ` Michael S. Tsirkin [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=20260618080405-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chenyichong@uniontech.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=rppt@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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