From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: HID: kye: Add report fixup for Genius Manticore Keyboard
Date: Sat, 30 Nov 2013 16:42:11 -0500 [thread overview]
Message-ID: <20131130214211.GA16854@redhat.com> (raw)
In-Reply-To: <20131128051223.28802660D26@gitolite.kernel.org>
> Commit: 4a2c94c9b6c03af61b04993340bd9559e2277de4
> Author: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> AuthorDate: Wed Nov 20 09:49:41 2013 -0500
> Committer: Jiri Kosina <jkosina@suse.cz>
> CommitDate: Thu Nov 21 10:28:58 2013 +0100
>
> HID: kye: Add report fixup for Genius Manticore Keyboard
>
> Genius Manticore Keyboard presents the same problem in its report
> descriptors than Genius Gila Gaming Mouse and Genius Imperator Keyboard.
> Use the same fixup.
..
> diff --git a/drivers/hid/hid-kye.c b/drivers/hid/hid-kye.c
> index 7384512..35a4f9c 100644
> --- a/drivers/hid/hid-kye.c
> +++ b/drivers/hid/hid-kye.c
> @@ -341,6 +341,9 @@ static __u8 *kye_report_fixup(struct hid_device *hdev, __u8 *rdesc,
> case USB_DEVICE_ID_GENIUS_GX_IMPERATOR:
> rdesc = kye_consumer_control_fixup(hdev, rdesc, rsize, 83,
> "Genius Gx Imperator Keyboard");
> + case USB_DEVICE_ID_GENIUS_MANTICORE:
> + rdesc = kye_consumer_control_fixup(hdev, rdesc, rsize, 104,
> + "Genius Manticore Keyboard");
> break;
Is the IMPERATOR case supposed to fall-through to MANTICORE here, or is there a missing break ?
The commit text describes using the same fixup, but has this alternative case.
Dave
next parent reply other threads:[~2013-11-30 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131128051223.28802660D26@gitolite.kernel.org>
2013-11-30 21:42 ` Dave Jones [this message]
2013-12-02 14:16 ` HID: kye: Add report fixup for Genius Manticore Keyboard Jiri Kosina
2013-12-02 14:28 ` Dave Jones
2013-12-02 14:31 ` Jiri Kosina
2013-12-02 14:32 ` Benjamin Tissoires
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=20131130214211.GA16854@redhat.com \
--to=davej@redhat.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.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