From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Juergen Gross <jgross@suse.com>
Cc: xen-devel@lists.xenproject.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, lyan@suse.com,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
andrii_chepurnyi@epam.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v5 1/3] xen: Sync up with the canonical protocol definitions in Xen
Date: Wed, 13 Jun 2018 08:49:31 +0300 [thread overview]
Message-ID: <3605901d-4a72-3f5a-6d74-cb13d2414a0b@gmail.com> (raw)
In-Reply-To: <20180612234020.GI38773@dtor-ws>
On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
> On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
>> On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
>>> From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>>
>>> This is the sync up with the canonical definitions of the input,
>>> sound and display protocols in Xen.
>>>
>>> Changes to kbdif:
>>> 1. Add missing string constants for {feature|request}-raw-pointer
>>> to align with the rest of the interface file.
>>>
>>> 2. Add new XenStore feature fields, so it is possible to individually
>>> control set of exposed virtual devices for each guest OS:
>>> - set feature-disable-keyboard to 1 if no keyboard device needs
>>> to be created
>>> - set feature-disable-pointer to 1 if no pointer device needs
>>> to be created
>>>
>>> 3. Move multi-touch device parameters to backend nodes: these are
>>> described as a part of frontend's XenBus configuration nodes
>>> while they belong to backend's configuration. Fix this by moving
>>> the parameters to the proper section.
>>>
>>> Unique-id field:
>>> 1. Add unique-id XenBus entry for virtual input and display.
>>>
>>> 2. Change type of unique-id field to string for sndif to align with
>>> display and input protocols.
>>>
>>> Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
>>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Reviewed-by: Juergen Gross <jgross@suse.com>
>>
>> I'm fine with this patch being added via the input tree with the other
>> patches. In case I should take it via the Xen tree, please send me a
>> note.
> Juergen,
>
> I created an immutable branch off v4.17 with these 3 patches in case you
> would want to merge them into your tree without waiting for them to
> appear in mainline:
>
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git ib/4.17-xen-kbdfront-runtime-config
>
> Thanks.
>
Thank you,
I would prefer the fastest path of course
next prev parent reply other threads:[~2018-06-13 5:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 7:48 [PATCH v5 0/3] Input: xen-kbdfront - allow better run-time configuration Oleksandr Andrushchenko
2018-06-12 7:48 ` [PATCH v5 1/3] xen: Sync up with the canonical protocol definitions in Xen Oleksandr Andrushchenko
2018-06-12 13:46 ` Juergen Gross
2018-06-12 13:47 ` Oleksandr Andrushchenko
2018-06-12 23:40 ` Dmitry Torokhov
2018-06-13 5:49 ` Oleksandr Andrushchenko [this message]
2018-06-13 6:11 ` Dmitry Torokhov
2018-06-13 6:13 ` Oleksandr Andrushchenko
2018-06-13 6:25 ` Dmitry Torokhov
2018-06-13 6:28 ` Oleksandr Andrushchenko
2018-06-13 6:40 ` Juergen Gross
2018-06-13 6:43 ` Oleksandr Andrushchenko
2018-06-12 7:48 ` [PATCH v5 2/3] Input: xen-kbdfront - fix multi-touch XenStore node's locations Oleksandr Andrushchenko
2018-06-12 13:47 ` Juergen Gross
2018-06-12 7:48 ` [PATCH v5 3/3] Input: xen-kbdfront - allow better run-time configuration Oleksandr Andrushchenko
2018-06-12 13:50 ` Juergen Gross
2018-06-12 22:07 ` Dmitry Torokhov
2018-06-13 5:47 ` 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=3605901d-4a72-3f5a-6d74-cb13d2414a0b@gmail.com \
--to=andr2000@gmail.com \
--cc=andrii_chepurnyi@epam.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyan@suse.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).