@@ -136,7 +136,7 @@ static bool have_full_constraints(void)
* regulator_lock_supply - lock a regulator and its supplies
* @rdev: regulator source
*/
-static void regulator_lock_supply(struct regulator_dev *rdev)
+static void __maybe_unused regulator_lock_supply(struct regulator_dev *rdev)
{
struct regulator *supply;
int i = 0;
@@ -156,7 +156,7 @@ static void regulator_lock_supply(struct regulator_dev *rdev)
* regulator_unlock_supply - unlock a regulator and its supplies
* @rdev: regulator source
*/
-static void regulator_unlock_supply(struct regulator_dev *rdev)
+static void __maybe_unused regulator_unlock_supply(struct regulator_dev *rdev)
{
struct regulator *supply;
Commit 9f01cd4a915e1 ("regulator: core: introduce function to lock regulators and its supplies") introduced a pair of new functions that are marked static but so far not used, which causes annoying but harmless compiler warnings: drivers/regulator/core.c:139:13: warning: 'regulator_lock_supply' defined but not used [-Wunused-function] static void regulator_lock_supply(struct regulator_dev *rdev) The best way to avoid these would be to add the code that will use these functions. If that still takes a while, this patch at least shuts up the compiler by marking the functions as __maybe_unused. The same could be achieved by marking them as static inline or non-static, or by hiding them from the compiler, but those seemed less appropriate. Signed-off-by: Arnd Bergmann <arnd@arndb.de> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/