linux-kernel - [PATCHv2 1/2] sched: Fixed cpupri_init stub signature; switched from macros to inlines.

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]

Date:	Mon, 20 Aug 2012 07:00:22 -0700
From:	Trevor Brandt <tjbrandt@...il.com>
To:	Trevor Brandt <tjbrandt@...il.com>,
	Josh Triplett <josh@...htriplett.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org
Cc:	team-fjord@...glegroups.com
Subject: [PATCHv2 1/2] sched: Fixed cpupri_init stub signature; switched from macros to inlines.

Fixed the cpupri_init stub in cpupri.h so it takes one argument
instead of none. At the same time, changed the cpupri stubs from
macros to inlines.

Signed-off-by: Trevor Brandt <tjbrandt@...il.com>
---
 kernel/sched/cpupri.h |    7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/kernel/sched/cpupri.h b/kernel/sched/cpupri.h
index f6d7561..fd7914c 100644
--- a/kernel/sched/cpupri.h
+++ b/kernel/sched/cpupri.h
@@ -27,8 +27,11 @@ void cpupri_set(struct cpupri *cp, int cpu, int pri);
 int cpupri_init(struct cpupri *cp);
 void cpupri_cleanup(struct cpupri *cp);
 #else
-#define cpupri_set(cp, cpu, pri) do { } while (0)
-#define cpupri_init() do { } while (0)
+static inline void cpupri_set(struct cpupri *cp, int cpu, int pri) { }
+static inline int cpupri_init(struct cpupri *cp)
+{
+	return 0;
+}
 #endif
 
 #endif /* _LINUX_CPUPRI_H */
-- 
1.7.9.5

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