linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elias Vanderstuyft <elias.vds@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>
Cc: "Simon Wood" <simon@mungewell.org>,
	linux-input <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Jiri Kosina" <jkosina@suse.cz>, Edwin <Edwin@velds.nl>,
	"Michal Malý" <madcatxster@devoid-pointer.net>,
	"Benjamin Tissoires" <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH 5/6] HID: Add vendor specific usage pages for Logitech G920
Date: Tue, 10 Nov 2015 22:38:27 +0100	[thread overview]
Message-ID: <CADbOyBQFFCpSrg36STiegvyBJwgFWwdcewhfxepuZ68DZjvY9Q@mail.gmail.com> (raw)
In-Reply-To: <CAN+gG=FTGXyV1heOpQb9Y=ZVRHhYP8=N-3jKgYq8OnqHgT=ikg@mail.gmail.com>

On Mon, Nov 9, 2015 at 9:20 AM, Benjamin Tissoires
<benjamin.tissoires@gmail.com> wrote:
> On Sat, Nov 7, 2015 at 5:10 PM, Simon Wood <simon@mungewell.org> wrote:
>> The Logitech G920 uses a couple of vendor specific usage pages,
>> which results in incorrect number of axis/buttons being detected.
>>
>> This patch adds these pages to the 'ignore' list.
>>
>> Reported-by: Elias Vanderstuyft <elias.vds@gmail.com>
>> Signed-off-by: Simon Wood <simon@mungewell.org>
>> ---
>>  drivers/hid/hid-input.c | 2 +-
>>  include/linux/hid.h     | 2 ++
>>  2 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
>> index 53aeaf6..c120be5 100644
>> --- a/drivers/hid/hid-input.c
>> +++ b/drivers/hid/hid-input.c
>> @@ -959,7 +959,7 @@ static void hidinput_configure_usage(struct hid_input *hidinput, struct hid_fiel
>>                 set_bit(EV_REP, input->evbit);
>>                 goto ignore;
>>
>> -       case HID_UP_LOGIVENDOR:
>> +       case HID_UP_LOGIVENDOR: case HID_UP_LOGIVENDOR2: case HID_UP_LOGIVENDOR3:
>
> One line per case, please.

This is my fault, I followed the convention used some lines above:
"case HID_GD_SLIDER: case HID_GD_DIAL: case HID_GD_WHEEL:"
but we expected this would get comments ;-)

Cheers,
Elias

  reply	other threads:[~2015-11-10 21:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 16:10 HID: Support for the Logitech G920 wheel Simon Wood
2015-11-07 16:10 ` [PATCH 1/6] INPUT: xpad: Add minimal support for Logitech G920 Wheel Simon Wood
2015-11-07 16:10 ` [PATCH 2/6] HID: hid-logitech-hidpp: Add support for very long packets Simon Wood
2015-11-07 16:10 ` [PATCH 3/6] HID: hid-logitech-hidpp: Add basic support for Logitech G920 Simon Wood
2015-11-09  8:11   ` Benjamin Tissoires
2015-11-07 16:10 ` [PATCH 4/6] HID: hid-logitech-hidpp: Add range sysfs " Simon Wood
2015-11-07 16:10 ` [PATCH 5/6] HID: Add vendor specific usage pages " Simon Wood
2015-11-09  8:20   ` Benjamin Tissoires
2015-11-10 21:38     ` Elias Vanderstuyft [this message]
2015-11-07 16:10 ` [PATCH 6/6] HID: hid-logitech-hidpp: G920 remove deadzones Simon Wood
2015-11-09  8:24   ` Benjamin Tissoires
2015-11-10 20:03     ` Simon Wood

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=CADbOyBQFFCpSrg36STiegvyBJwgFWwdcewhfxepuZ68DZjvY9Q@mail.gmail.com \
    --to=elias.vds@gmail.com \
    --cc=Edwin@velds.nl \
    --cc=benjamin.tissoires@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madcatxster@devoid-pointer.net \
    --cc=simon@mungewell.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).