Linux Support On The Way For The ASUS ROG Raikiri Controller

[phoronix]

Phoronix: Linux Support On The Way For The ASUS ROG Raikiri Controller

Linux driver support is forthcoming for the ASUS ROG Raikiri gaming controller...

https://www.phoronix.com/news/ASUS-ROG-Raikiri-Linux

[nvaert1986]

Question: How can I actually have a patch for a device added to a kernel? I created a bug report for the 8BitDo Ultimate Wired Controller for Xbox. I eventually created a patch myself (as it was a simple one liner) and sent a mail to a few kernel maintainers (as there was nobody directly in the MAINTAINERS file for input / game pads, but never got a response. Are they too busy / overburdened or am I doing something wrong? Currently I'm just applying the patch to each new kernel that I compile.

Relevant kernel bug and patch: https://bugzilla.kernel.org/show_bug.cgi?id=218370
Guide I followed for submitting the patch: https://www.kernel.org/doc/html/v6.6...g-patches.html

[aleksamagicka]

Question: How can I actually have a patch for a device added to a kernel? I created a bug report for the 8BitDo Ultimate Wired Controller for Xbox. I eventually created a patch myself (as it was a simple one liner) and sent a mail to a few kernel maintainers (as there was nobody directly in the MAINTAINERS file for input / game pads, but never got a response. Are they too busy / overburdened or am I doing something wrong? Currently I'm just applying the patch to each new kernel that I compile.

Relevant kernel bug and patch: https://bugzilla.kernel.org/show_bug.cgi?id=218370
Guide I followed for submitting the patch: https://www.kernel.org/doc/html/v6.6...g-patches.html

Not sure what you've sent, but you need to:

1. Branch off the correct repo for the input subsystem
2. Make your change(s), separated into logical commits with clear descriptions (here, you'd only need one)
3. git format-patch that commit to get a patch as .patch
4. Run ./scripts/checkpatch.pl --strict on that patch file and fix everything it says
5. Use ./scripts/get_maintainers.pl --norolestats to get a list of emails to which you should send (there are entries in MAINTAINERS, if only the mailing lists, and this will also look at people who committed to the file, so use it)
6. git send-email the patch and be ready for a response

Picking a few emails and sending something akin to "hey look at bugzilla and include please" is not the correct protocol (not saying that you did that per se).

[aschmidtm]

What are read controls?