| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 30 Nov 2012 13:54:06 -0800 From: Chris Moeller <kode54@...il.com> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org, Chris Moeller <kode54@...il.com> Subject: [PATCH v2 0/1] Input: xpad - Implement wireless controller LED setting and fix connect time LED setting I've submitted versions of this with prior patch sets, and this part was never accepted, possibly because it depended on other patches to work, or possibly because it wasn't so cleanly organized. This time, I've split the LED setting command off into its own static function, then call that on controller connect and optionally on LED setting commands. The static function does not include any locking, because locking inside the function which receives the incoming packets deadlocks the driver, and does not appear to be necessary anyway. It also removes all traces of the original bulk out function which was designed for the purpose of setting the LED status on connect, as I found that it actually does not work at all. It appears to try to send the data, but nothing actually happens to the controller LEDs. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists