From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Oleksandr Andrushchenko <andr2000@gmail.com>
Cc: xen-devel@lists.xenproject.org, alsa-devel@alsa-project.org,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [Xen-devel] [PATCH 1/2] sndif: introduce protocol version
Date: Thu, 1 Mar 2018 17:12:18 -0500 [thread overview]
Message-ID: <20180301221218.GD32676@char.us.oracle.com> (raw)
In-Reply-To: <1517819100-1029-2-git-send-email-andr2000@gmail.com>
On Mon, Feb 05, 2018 at 10:24:59AM +0200, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> Protocol version was referenced in the protocol description,
> but missed its definition. Fix this by adding a constant
> for current protocol version.
>
> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Thank you!
> ---
> xen/include/public/io/sndif.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/xen/include/public/io/sndif.h b/xen/include/public/io/sndif.h
> index c5c1978406b3..b0e6ac35e131 100644
> --- a/xen/include/public/io/sndif.h
> +++ b/xen/include/public/io/sndif.h
> @@ -38,6 +38,13 @@
>
> /*
> ******************************************************************************
> + * Protocol version
> + ******************************************************************************
> + */
> +#define XENSND_PROTOCOL_VERSION "1"
> +
> +/*
> + ******************************************************************************
> * Feature and Parameter Negotiation
> ******************************************************************************
> *
> --
> 2.7.4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-01 22:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 8:24 [PATCH 0/2] sndif: add explicit back and front synchronization Oleksandr Andrushchenko
2018-02-05 8:24 ` [PATCH 1/2] sndif: introduce protocol version Oleksandr Andrushchenko
2018-03-01 22:12 ` Konrad Rzeszutek Wilk [this message]
2018-02-05 8:25 ` [PATCH 2/2] sndif: add explicit back and front synchronization Oleksandr Andrushchenko
2018-03-01 22:11 ` [Xen-devel][PATCH " Konrad Rzeszutek Wilk
2018-03-02 6:30 ` Oleksandr Andrushchenko
2018-02-19 6:31 ` [Xen-devel][PATCH 0/2] " Oleksandr Andrushchenko
2018-03-01 6:29 ` Oleksandr Andrushchenko
2018-03-02 16:52 ` Oleksandr Andrushchenko
2018-03-06 10:52 ` Takashi Iwai
2018-03-06 11:25 ` Oleksandr Andrushchenko
2018-03-06 11:32 ` Takashi Iwai
2018-03-06 12:05 ` Oleksandr Andrushchenko
2018-03-06 12:52 ` Takashi Iwai
2018-03-06 13:30 ` Oleksandr Andrushchenko
2018-03-06 13:48 ` Takashi Iwai
2018-03-06 14:13 ` Oleksandr Andrushchenko
2018-03-06 14:27 ` Takashi Iwai
2018-03-06 14:48 ` Oleksandr Andrushchenko
2018-03-06 15:06 ` Takashi Iwai
2018-03-06 16:04 ` Oleksandr Andrushchenko
2018-03-06 16:30 ` Takashi Iwai
2018-03-07 8:49 ` Oleksandr Andrushchenko
2018-03-11 8:15 ` Takashi Iwai
2018-03-12 6:26 ` Oleksandr Andrushchenko
2018-03-13 11:49 ` Oleksandr Andrushchenko
2018-03-13 16:31 ` Takashi Iwai
2018-03-13 17:31 ` Oleksandr Andrushchenko
2018-03-13 18:48 ` Takashi Iwai
2018-03-14 7:32 ` Oleksandr Andrushchenko
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=20180301221218.GD32676@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=andr2000@gmail.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=xen-devel@lists.xenproject.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).