| commit | 198bbc67b7ca17e443e3056b8e14cd60a96e2d8d | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Tue, 24 Mar 2009 06:52:58 +0000 (24 03:52 -0300) | ||
| committer | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Tue, 24 Mar 2009 06:52:58 +0000 (24 03:52 -0300) | ||
| tree | abd4d8530d1bc295505091d8f31f090fde2561ff | treesnapshot (tar.gz zip) |
| parent | ef798b3deb4327f1c1278294c013c4229fc72f0f | commitdiff |
rfkill: add __must_check annotations
rfkill is not a small, mere detail in wireless support. Once it starts
supporting rfkill and users start counting on that support, a wireless
device is at risk of operating in dangerous conditions should rfkill
support fail to properly activate.
Therefore, add the required __must_check annotations on some key functions
of the rfkill API, for which the wireless drivers absolutely MUST handle
the failure mode safely in order to avoid a potentially dangerous situation
where the wireless transmitter is left enabled when the user don't want it
to.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
rfkill is not a small, mere detail in wireless support. Once it starts
supporting rfkill and users start counting on that support, a wireless
device is at risk of operating in dangerous conditions should rfkill
support fail to properly activate.
Therefore, add the required __must_check annotations on some key functions
of the rfkill API, for which the wireless drivers absolutely MUST handle
the failure mode safely in order to avoid a potentially dangerous situation
where the wireless transmitter is left enabled when the user don't want it
to.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
| include/linux/rfkill.h | diffblobblamehistory | |
| net/rfkill/rfkill.c | diffblobblamehistory |