All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Todd Kelner <tsopdump@gmail.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: sony: Add touchpad support for Sony's NSG-MR5U and NSG-MR7U remotes
Date: Mon, 31 Jul 2017 16:01:28 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1707311559340.4705@cbobk.fhfr.pm> (raw)
In-Reply-To: <20170211050004.GA3944@gmail.com>

On Fri, 10 Feb 2017, Todd Kelner wrote:

> Sony's NSG-MR5U and NSG-MR7U remote controls have a full keyboard and a
> touchpad.  The keyboard is already supported by the existing Linux kernel
> and drivers but the touchpad is not recognized.  This patch adds the code
> needed to bring full functionality to the touchpad.
> 
> Note that these remotes use the vendor code for SMK even though they are
> Sony branded.

Ouch, sorry for missing this. I've just found this patch hiding in a dark 
corners of my inbox.

[ ... snip ... ]
>  	/* We map the button underneath the touchpad to BTN_LEFT. */
>  	__set_bit(EV_KEY, sc->touchpad->evbit);
>  	__set_bit(BTN_LEFT, sc->touchpad->keybit);
> +	__clear_bit(BTN_MIDDLE, sc->touchpad->keybit);
> +	__clear_bit(BTN_RIGHT, sc->touchpad->keybit);

Could you please explain (perhaps in a comment and/or commitlog) why this 
change is okay even in !(sc->quirks & NSG_MRXU_REMOTE) cases?

Otherwise the patch looks good to me; if you could please rebase it on top 
of current codebase, I'll merge it immediately.

Thanks,

-- 
Jiri Kosina
SUSE Labs


  parent reply	other threads:[~2017-07-31 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11  5:00 [PATCH] HID: sony: Add touchpad support for Sony's NSG-MR5U and NSG-MR7U remotes Todd Kelner
2017-03-21 14:06 ` Jiri Kosina
2017-03-21 23:56   ` Colenbrander, Roelof
2017-03-22  1:10     ` Colenbrander, Roelof
2017-03-24 14:15       ` Jiri Kosina
2017-07-31 14:01 ` Jiri Kosina [this message]
     [not found] <20170128023942.GA11682@gmail.com>
     [not found] ` <20170130095618.GA26482@mail.corp.redhat.com>
     [not found]   ` <20170131000243.GA3725@gmail.com>
     [not found]     ` <20170201085358.GE31658@mail.corp.redhat.com>
2017-02-01  8:56       ` Benjamin Tissoires
  -- strict thread matches above, loose matches on Subject: below --
2017-01-28  2:42 Todd Kelner

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.LSU.2.20.1707311559340.4705@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=tsopdump@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 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.