summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlan Jenkins <alan-jenkins@tuffmail.co.uk>2009-07-18 19:20:20 +0100
committerJohn W. Linville <linville@tuxdriver.com>2009-07-21 12:07:43 -0400
commite56f0975360369347725c49654ecfe3792710429 (patch)
tree52845ecc6fca6a66c192f87eb8d3d45b0ddbce18
parentc66284f2a421f6aebbafd56cb8b90b8e6a9cb2de (diff)
downloadop-kernel-dev-e56f0975360369347725c49654ecfe3792710429.zip
op-kernel-dev-e56f0975360369347725c49654ecfe3792710429.tar.gz
rfkill: remove too-strict __must_check
Some drivers don't need the return value of rfkill_set_hw_state(), so it should not be marked as __must_check. Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk> Acked-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
-rw-r--r--include/linux/rfkill.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
index 2ce2983..278777fa 100644
--- a/include/linux/rfkill.h
+++ b/include/linux/rfkill.h
@@ -224,7 +224,7 @@ void rfkill_destroy(struct rfkill *rfkill);
* should be blocked) so that drivers need not keep track of the soft
* block state -- which they might not be able to.
*/
-bool __must_check rfkill_set_hw_state(struct rfkill *rfkill, bool blocked);
+bool rfkill_set_hw_state(struct rfkill *rfkill, bool blocked);
/**
* rfkill_set_sw_state - Set the internal rfkill software block state
OpenPOWER on IntegriCloud