From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: akpm@linux-foundation.org, eperezma@redhat.com,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
ljs@kernel.org, rppt@kernel.org, virtualization@lists.linux.dev,
xuanzhuo@linux.alibaba.com
Subject: Re: [PATCH 0/2] tools: Fix tools/virtio test build
Date: Mon, 22 Jun 2026 07:54:12 -0400 [thread overview]
Message-ID: <20260622075317-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <A1DCE9FEF645A3F9+20260622070113.1207518-1-chenyichong@uniontech.com>
On Mon, Jun 22, 2026 at 03:01:13PM +0800, Yichong Chen wrote:
> Hi Michael,
>
> I checked the history again. The tree was based on v7.1, but I had
> unrelated local commits on top when I generated the series.
>
> I rechecked this on a clean v7.1 tree:
>
> 8cd9520d35a6 ("Linux 7.1")
>
> The build failure is still reproducible with:
>
> make -C tools/virtio test
>
> The first failure is:
>
> include/linux/virtio.h:10:10: fatal error:
> linux/mod_devicetable.h: No such file or directory
>
> The two patches also apply cleanly on top of v7.1 and make
> the tools/virtio test target build virtio_test, vringh_test and
> vhost_net_test.
>
> I can resend a v2 based on v7.1 with a base-commit if you prefer.
>
> Thanks,
> Yichong
Hello, thanks for the report!
the commit to try is 8cb2c9285e4ce9154f45fb15633ebd45dfd8d9cf - that is
not in 7.1.
prev parent reply other threads:[~2026-06-22 11:54 UTC|newest]
Thread overview: 4+ 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
2026-06-22 7:01 ` Yichong Chen
2026-06-22 11:54 ` 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=20260622075317-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 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.