From: Nikolai Kondrashov <spbnick@gmail.com>
To: milan.plzik@gmail.com, jkosina@suse.cz
Cc: digimend-devel@lists.sourceforge.net, linux-input@vger.kernel.org
Subject: Re: [DIGImend-devel] [PATCH] Fix report descriptor for Genius PenSketch M912
Date: Mon, 16 Feb 2015 12:10:19 +0200 [thread overview]
Message-ID: <54E1C20B.2090108@gmail.com> (raw)
In-Reply-To: <1423903724-18792-1-git-send-email-milan.plzik@gmail.com>
On 02/14/2015 10:48 AM, milan.plzik@gmail.com wrote:
> From: Milan Plzik <milan.plzik@gmail.com>
>
> Genius PenSketch M912 digitizer tablet sends incorrect report descriptor by
> default. This patch replaces it with a corrected one.
>
> Signed-off-by: Milan Plzik <milan.plzik@gmail.com>
I reviewed this on digimend-devel a while ago, looks good to me.
Thanks, Milan!
Reviewed-by: Nikolai Kondrashov <spbnick@gmail.com>
Nick
next prev parent reply other threads:[~2015-02-16 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 8:48 [PATCH] Fix report descriptor for Genius PenSketch M912 milan.plzik
2015-02-16 10:10 ` Nikolai Kondrashov [this message]
2015-02-17 12:16 ` [DIGImend-devel] " Jiri Kosina
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=54E1C20B.2090108@gmail.com \
--to=spbnick@gmail.com \
--cc=digimend-devel@lists.sourceforge.net \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=milan.plzik@gmail.com \
/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).