All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] HID: multitouch: Add support for button type usage
Date: Thu, 12 Mar 2015 00:06:06 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1503120005500.24876@pobox.suse.cz> (raw)
In-Reply-To: <20150312011318.GE19872@mail.corp.redhat.com>

On Wed, 11 Mar 2015, Benjamin Tissoires wrote:

> On Mar 11 2015 or thereabouts, Seth Forshee wrote:
> > According to [1], Windows Precision Touchpad devices must supply
> > a button type usage in the device capabilities feature report. A
> > value of 0 indicates that the device contains a depressible
> > button (i.e. it's a click-pad) whereas a value of 1 indicates
> > a non-depressible button. Add support for this usage and set
> > INPUT_PROP_BUTTONPAD on the touchpad input device whenever a
> > depressible button is present.
> > 
> > [1] https://msdn.microsoft.com/en-us/library/windows/hardware/dn467314(v=vs.85).aspx
> > 
> > Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
> > ---
> 
> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> 
> Thanks for the quick re-spin

Applied to for-4.1/multitouch.

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2015-03-12  4:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 21:00 [PATCH] HID: multitouch: Add support for button type usage Seth Forshee
2015-03-01  3:34 ` [PATCH v2] " Seth Forshee
2015-03-11 16:19   ` Jiri Kosina
2015-03-11 17:25     ` Seth Forshee
2015-03-11 17:29       ` [PATCH v3] " Seth Forshee
2015-03-11 20:55         ` Benjamin Tissoires
2015-03-11 21:55           ` Seth Forshee
2015-03-11 22:26             ` [PATCH v4] " Seth Forshee
2015-03-12  1:13               ` Benjamin Tissoires
2015-03-12  4:06                 ` Jiri Kosina [this message]

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=alpine.LNX.2.00.1503120005500.24876@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seth.forshee@canonical.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 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.