From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: "Oleksandr_Andrushchenko@epam.com"
<Oleksandr_Andrushchenko@epam.com>,
xen-devel@lists.xenproject.org, konrad.wilk@oracle.com,
jgross@suse.com
Subject: Re: [PATCH v2 0/4] Unique-id and fixes to some protocols
Date: Fri, 8 Jun 2018 15:52:40 +0300 [thread overview]
Message-ID: <6f9e24b2-7a5c-eabb-92c8-4294807bd6cf@gmail.com> (raw)
In-Reply-To: <20180608060831.20194-1-andr2000@gmail.com>
On 06/08/2018 09:08 AM, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>
> Hi, all!
>
> This series fixes inconsistency in section used while defining kbdif
> XenBus entries and adds string "unique-id" XenBus entry missing in
> displif and kbdif. It also changes sndif's "unique-id" field from
> integer to string to be aligned with displif/kbdif.
>
> Konrad, I added your r-b tags to *all* the patches, so please
> let me know if I have to drop those (if this is not what you meant
> on the mailing-list).
>
> Juergen, could you please release ack the rest of the patches as these
> are needed to add sound configuration to libxl/xl and extend input
> to support multi-touch. These are the changes to header files which are
> not involved in Xen build, so it seems to be safe.
> This will also unblock ptorocol synchronization with Linux, so I can
> push an extension to xen-kbdfront driver (disable feature).
>
> Thank you,
> Oleksandr Andrushchenko
>
> Changes since v1:
> - Changed type of "unique-id" from uint32_t to string (Konrad)
> - Added r-b's
>
> Oleksandr Andrushchenko (4):
> xen/kbdif: Move multi-touch device parameters to backend nodes
> xen/kbdif: Add unique input device identifier
> xen/displif: Add unique display connector identifier
> xen/sndif: Change stream's unique-id to string
>
> xen/include/public/io/displif.h | 8 ++++++
> xen/include/public/io/kbdif.h | 48 ++++++++++++++++++++-------------
> xen/include/public/io/sndif.h | 10 +++----
> 3 files changed, 41 insertions(+), 25 deletions(-)
>
Konrad, if the patches seem to be ok, could you please
commit those?
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-06-08 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 6:08 [PATCH v2 0/4] Unique-id and fixes to some protocols Oleksandr Andrushchenko
2018-06-08 6:08 ` [PATCH v2 1/4] xen/kbdif: Move multi-touch device parameters to backend nodes Oleksandr Andrushchenko
2018-06-08 6:08 ` [PATCH v2 2/4] xen/kbdif: Add unique input device identifier Oleksandr Andrushchenko
2018-06-08 12:40 ` Juergen Gross
2018-06-08 6:08 ` [PATCH v2 3/4] xen/displif: Add unique display connector identifier Oleksandr Andrushchenko
2018-06-08 12:41 ` Juergen Gross
2018-06-08 6:08 ` [PATCH v2 4/4] xen/sndif: Change stream's unique-id to string Oleksandr Andrushchenko
2018-06-08 12:42 ` Juergen Gross
2018-06-08 12:52 ` Oleksandr Andrushchenko [this message]
2018-06-08 14:58 ` [PATCH v2 0/4] Unique-id and fixes to some protocols Konrad Rzeszutek Wilk
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=6f9e24b2-7a5c-eabb-92c8-4294807bd6cf@gmail.com \
--to=andr2000@gmail.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.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 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.