From: JackStocker <jackstocker.93@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Seth Forshee <seth.forshee@canonical.com>,
Dmitry Fleytman <dmitry@daynix.com>,
Devin Heitmueller <dheitmueller@kernellabs.com>,
Sandeep Singh <sandeep.singh@amd.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v3] Add delay-init quirk for Corsair K70 RGB keyboards
Date: Thu, 15 Feb 2018 17:59:34 +0000 [thread overview]
Message-ID: <5ffac152-c7e8-357f-9fee-c255d7947ecc@gmail.com> (raw)
On 15/02/18 17:35, Greg Kroah-Hartman wrote:
> On Sun, Feb 04, 2018 at 04:50:58PM +0000, JackStocker wrote:
>> Following on from this patch: https://lkml.org/lkml/2017/11/3/516,
>> Corsair K70 RGB keyboards also require the DELAY_INIT quirk to
>> start correctly at boot.
>>
>> Device ids found here:
>> usb 3-3: New USB device found, idVendor=1b1c, idProduct=1b13
>> usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> usb 3-3: Product: Corsair K70 RGB Gaming Keyboard
>>
>> Signed-off-by: JackStocker <jackstocker.93@gmail.com>
> I need a "real" name here please.
>
> thanks,
>
> greg k-h
As in 'Jack Stocker' is that correct?
Cheers,
Jack
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-02-15 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:59 JackStocker [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 18:02 [v3] Add delay-init quirk for Corsair K70 RGB keyboards Greg Kroah-Hartman
2018-02-15 17:35 Greg Kroah-Hartman
2018-02-04 16:50 JackStocker
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=5ffac152-c7e8-357f-9fee-c255d7947ecc@gmail.com \
--to=jackstocker.93@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=dmitry@daynix.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=sandeep.singh@amd.com \
--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 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).