All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liam R. Howlett (Google)" <liam@infradead.org>
To: "Michael S . Tsirkin" <mst@redhat.com>,
	"Jason Wang" <jasowangio@gmail.com>,
	"Eugenio Pérez" <eperezma@redhat.com>
Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Liam R. Howlett (Google)" <liam@infradead.org>
Subject: [PATCH 0/2] tools/virtio: fix the build and the posix_memalign() checks
Date: Mon, 19 Oct 2026 23:29:56 -0400	[thread overview]
Message-ID: <20261020032958.1930203-1-liam@infradead.org> (raw)

Working on other tools, I came across the fact that posix_memalign()'s
return is not the standard negative error.  Scanning the git repo, I
came across the virtio issue with the return.  Testing turned out the be
broke as well, so there's a patch to fix testing prior to fixing the
caller.

Liam R. Howlett (Google) (2):
  tools/virtio: add a shim for linux/device-id/virtio.h
  tools/virtio: check posix_memalign() for failure

 tools/virtio/linux/device-id/virtio.h | 2 ++
 tools/virtio/linux/kernel.h           | 3 ++-
 tools/virtio/vhost_net_test.c         | 2 +-
 tools/virtio/virtio_test.c            | 2 +-
 4 files changed, 6 insertions(+), 3 deletions(-)
 create mode 100644 tools/virtio/linux/device-id/virtio.h

-- 
2.47.3


             reply	other threads:[~2026-10-20  3:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20  3:29 Liam R. Howlett (Google) [this message]
2026-10-20  3:29 ` [PATCH 1/2] tools/virtio: add a shim for linux/device-id/virtio.h Liam R. Howlett (Google)
2026-10-20  8:16   ` sashiko-bot
2026-10-20  3:29 ` [PATCH 2/2] tools/virtio: check posix_memalign() for failure Liam R. Howlett (Google)
2026-10-20  8:18   ` sashiko-bot
2026-10-21  9:44   ` Eugenio Perez Martin

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=20261020032958.1930203-1-liam@infradead.org \
    --to=liam@infradead.org \
    --cc=eperezma@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=u.kleine-koenig@baylibre.com \
    --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.