From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Iurii Konovalenko <iurii.konovalenko@globallogic.com>,
Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>,
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] sndif: add ABI for Para-virtual sound
Date: Tue, 20 Jan 2015 12:01:52 +0000 [thread overview]
Message-ID: <1421755312.10440.246.camel@citrix.com> (raw)
In-Reply-To: <54BE3AC5.2080005@citrix.com>
On Tue, 2015-01-20 at 12:23 +0100, Roger Pau Monné wrote:
> In general I would prefer any new protocol that's added to Xen to be
> described with plain binary layouts, just like protocols are usually
> written. For example like it's done in:
> http://tools.ietf.org/html/rfc793#page-15.
>
> Providing suitable structs would be a bonus, but not a way to describe it.
This is an interesting proposal, but it is a radical departure from how
we've done things until now so I think it deserves higher billing than a
comment at the end of hundreds of lines of untrimmed quotes.
I think given the change it would be best to discuss this in a new
dedicated thread, independent from any particular new protocol
contribution which might be going on.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-01-20 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 10:22 [PATCH v2] sndif: add ABI for Para-virtual sound Oleksandr Dmytryshyn
2015-01-20 11:00 ` Andrew Cooper
2015-01-20 11:23 ` Roger Pau Monné
2015-01-20 12:01 ` Ian Campbell [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=1421755312.10440.246.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=iurii.konovalenko@globallogic.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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.