Here is a small set of fixes for rfkill, mostly stuff I noticed while I
was working on other patches that I will send in for RFC and testing,
later.
It does include the documentation change requested by Ivo that makes
rfkill_force_state non-optional where applicable (devices that get
external state changes).
Shortlog:
Henrique de Moraes Holschuh (4):
rfkill: document rfkill_force_state as required
rfkill: fix led-trigger unregister order in error unwind
rfkill: document the rfkill struct locking
rfkill: mutex fixes
Please consider for merging for 2.6.26, as they are fixes and not
enhancements. Ivo, please be specially hard on the last patch, I did
test it here, but locking is always tricky...
Patches based on wireless-testing master.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
