All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
	"virtualization@lists.linux-foundation.org" 
	<virtualization@lists.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/virtio: Fix build
Date: Sun, 13 Oct 2019 15:29:34 +0200	[thread overview]
Message-ID: <eacb6818-fe3e-f983-9946-e172f0077d4b@web.de> (raw)
In-Reply-To: <20191013081541-mutt-send-email-mst@kernel.org>

On 13.10.19 14:20, Michael S. Tsirkin wrote:
> On Sun, Oct 13, 2019 at 02:01:03PM +0200, Jan Kiszka wrote:
>> On 13.10.19 13:52, Michael S. Tsirkin wrote:
>>> On Sun, Oct 13, 2019 at 11:03:30AM +0200, Jan Kiszka wrote:
>>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>>
>>>> Various changes in the recent kernel versions broke the build due to
>>>> missing function and header stubs.
>>>>
>>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> Thanks!
>>> I think it's already fixes in the vhost tree.
>>> That tree also includes a bugfix for the test.
>>> Can you pls give it a spin and report?
>>
>> Mostly fixed: the xen_domain stup is missing.
>>
>> Jan
>
> That's in xen/xen.h. Do you still see any build errors?

ca16cf7b30ca79eeca4d612af121e664ee7d8737 lacks this - forgot to add to
some commit?

Jan

  parent reply	other threads:[~2019-10-13 13:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13  9:03 [PATCH] tools/virtio: Fix build Jan Kiszka
2019-10-13 11:52 ` Michael S. Tsirkin
2019-10-13 12:01   ` Jan Kiszka
2019-10-13 12:20     ` Michael S. Tsirkin
2019-10-13 12:20     ` Michael S. Tsirkin
2019-10-13 13:29       ` Jan Kiszka
2019-10-13 13:29       ` Jan Kiszka [this message]
2019-10-13 13:39         ` Michael S. Tsirkin
2019-10-13 13:39         ` Michael S. Tsirkin
2019-10-13 12:01   ` Jan Kiszka
2019-10-13 11:52 ` Michael S. Tsirkin
2019-10-13  9:03 Jan Kiszka
2022-07-05  7:22 [PATCH] tools/virtio: fix build Stefano Garzarella
2022-07-05  7:22 ` Stefano Garzarella
2022-07-06  6:39 ` 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=eacb6818-fe3e-f983-9946-e172f0077d4b@web.de \
    --to=jan.kiszka@web.de \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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.