From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH 0/2] xen,input: xen-kbdfront pointing device resolution support
Date: Tue, 4 Apr 2017 13:58:57 +0200 [thread overview]
Message-ID: <ffacba2c-e86f-eacc-b76c-8434871022a3@suse.com> (raw)
In-Reply-To: <20170321171905.31584-1-jgross@suse.com>
On 21/03/17 18:19, Juergen Gross wrote:
> As my patch tying the resolution of the xen pointing device to that of
> the framebuffer wasn't accepted add support for different resolutions
> via a module parameter.
>
> Another possibility would be to set parameters via Xenstore, but this
> is broken (patch 2 fixes that) and not yet supported by Xen tools.
>
> Juergen Gross (2):
> xen,input: add xen-kbdfront module parameter for setting resolution
> xen,input: repair xen-kbdfront resolution setting via xenstore
>
> drivers/input/misc/xen-kbdfront.c | 42 ++++++++++++++++++++++++++-------------
> 1 file changed, 28 insertions(+), 14 deletions(-)
>
Ping?
Juergen
next prev parent reply other threads:[~2017-04-04 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 17:19 [PATCH 0/2] xen, input: xen-kbdfront pointing device resolution support Juergen Gross
2017-03-21 17:19 ` [PATCH 1/2] xen, input: add xen-kbdfront module parameter for setting resolution Juergen Gross
2017-04-10 13:44 ` [Xen-devel] " Oleksandr Andrushchenko
2017-04-10 13:50 ` Juergen Gross
2017-04-10 14:00 ` Oleksandr Andrushchenko
2017-04-10 14:11 ` Juergen Gross
2017-04-10 14:18 ` Oleksandr Andrushchenko
2017-04-11 8:54 ` Juergen Gross
2017-03-21 17:19 ` [PATCH 2/2] xen, input: repair xen-kbdfront resolution setting via xenstore Juergen Gross
2017-04-10 14:20 ` [Xen-devel] " Oleksandr Andrushchenko
2017-04-04 11:58 ` Juergen Gross [this message]
2017-04-07 13:45 ` [Xen-devel] [PATCH 0/2] xen, input: xen-kbdfront pointing device resolution support 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=ffacba2c-e86f-eacc-b76c-8434871022a3@suse.com \
--to=jgross@suse.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).