linux-kernel - [PATCH] timekeeping: Fix build when generic clockevents are enabled

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1344513580-9571-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Date:	Thu,  9 Aug 2012 12:59:40 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Thomas Gleixner <tglx@...utronix.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel@...r.kernel.org,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: [PATCH] timekeeping: Fix build when generic clockevents are enabled

Commit a2c204 (timekeeping: Add suspend and resume of clock event devices)
added suspend and resume operations for clockevents but did not provide
stubs for these functions, breaking the build when clockevents are not
being built. Add the stubs.

Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
---
 include/linux/clockchips.h |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h
index ca060db..4f9c280 100644
--- a/include/linux/clockchips.h
+++ b/include/linux/clockchips.h
@@ -170,6 +170,8 @@ extern void clockevents_notify(unsigned long reason, void *arg);
 #else /* CONFIG_GENERIC_CLOCKEVENTS_BUILD */
 
 #define clockevents_notify(reason, arg) do { } while (0)
+#define clockevents_suspend() do { } while (0)
+#define clockevents_resume() do { } while (0)
 
 #endif
 
-- 
1.7.10.4

--
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/