qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: qemu-devel@nongnu.org, "Hanna Czenczek" <hreitz@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	"Albert Esteve" <aesteve@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Alex Benné e" <alex.bennee@linaro.org>
Subject: Re: [PATCH] vhost-user: Fix protocol feature bit conflict
Date: Mon, 16 Oct 2023 15:01:42 +0300	[thread overview]
Message-ID: <2mew1.gewqf1fewie@linaro.org> (raw)
In-Reply-To: <20231016103254.7xrnptmwrjnsr3uc@vireshk-i7>

On Mon, 16 Oct 2023 13:32, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>Perhaps because we will never use it from Qemu code ?

It'd be nice if downstream users of the vhost-user protocol can fetch 
and use the header verbatim. For example, for automatically generating 
bindings.


  parent reply	other threads:[~2023-10-16 12:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  8:32 [PATCH] vhost-user: Fix protocol feature bit conflict Hanna Czenczek
2023-10-16  8:45 ` Manos Pitsidianakis
2023-10-16 10:32   ` Viresh Kumar
2023-10-16 11:40     ` Alex Bennée
2023-10-17  5:36       ` Viresh Kumar
2023-10-17  7:51         ` Hanna Czenczek
2023-10-17  7:53           ` Viresh Kumar
2023-10-17  8:14             ` Hanna Czenczek
2023-10-17  8:16               ` Viresh Kumar
2023-10-17  8:25             ` Albert Esteve
2023-10-17 10:56               ` Stefan Hajnoczi
2023-10-17 14:38                 ` Albert Esteve
2023-10-17 14:46                   ` Stefan Hajnoczi
2023-10-16 12:01     ` Manos Pitsidianakis [this message]
2023-10-16 10:40   ` Hanna Czenczek
2023-10-16 10:13 ` Stefano Garzarella
2023-10-16 14:03 ` Stefan Hajnoczi

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=2mew1.gewqf1fewie@linaro.org \
    --to=manos.pitsidianakis@linaro.org \
    --cc=aesteve@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=hreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).