From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: xen-devel@lists.xenproject.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
jgross@suse.com, lyan@suse.com, boris.ostrovsky@oracle.com
Cc: konrad.wilk@oracle.com, andr2000@gmail.com,
andrii_chepurnyi@epam.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: [PATCH v5 0/3] Input: xen-kbdfront - allow better run-time configuration
Date: Tue, 12 Jun 2018 10:48:53 +0300 [thread overview]
Message-ID: <20180612074856.28451-1-andr2000@gmail.com> (raw)
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Hi, all!
This patch series synchronizes Xen canonical protocol definitions
which allow the last two patches in the series to update Xen
kbdfront driver with a fix and v5 of the patch to allow better
run-time configuration for xen-kbdfront.
As xen-kbdfront patches rely on protocol changes from patch 1 I am
sending these all together: Boris, Juergen, if you and Dmitry do not
mind, can we have patch 1 applied through Dmitry's tree?
Thank you,
Oleksandr
Changes since v4:
- Added required changes to Xen protocols
- Added a fix for multi-touch XenStore node's locations
- No changes to "Input: xen-kbdfront - allow better run-time
configuration"
Changes since v3:
- do not connect backend if all virtual devices are disabled (Dmitry)
Changes since v2:
- based on XenStore kbdif features to control which devices are
exposed instead of module parameters.
Oleksandr Andrushchenko (3):
xen: Sync up with the canonical protocol definitions in Xen
Input: xen-kbdfront - fix multi-touch XenStore node's locations
Input: xen-kbdfront - allow better run-time configuration
drivers/input/misc/xen-kbdfront.c | 183 +++++++++++++++++------------
include/xen/interface/io/displif.h | 8 ++
include/xen/interface/io/kbdif.h | 78 +++++++++---
include/xen/interface/io/sndif.h | 10 +-
4 files changed, 180 insertions(+), 99 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-12 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 7:48 Oleksandr Andrushchenko [this message]
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
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=20180612074856.28451-1-andr2000@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).