linux-kernel - Re: [PATCH v2 3/6] sched/cpupri: Remove unnecessary definitions in cpupri.h

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141104093913.392d2ed2@gandalf.local.home>
Date:	Tue, 4 Nov 2014 09:39:13 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"pang.xunlei" <pang.xunlei@...aro.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Juri Lelli <juri.lelli@...il.com>
Subject: Re: [PATCH v2 3/6] sched/cpupri: Remove unnecessary definitions in
 cpupri.h

On Tue,  4 Nov 2014 19:13:02 +0800
"pang.xunlei" <pang.xunlei@...aro.org> wrote:

> Actually, cpupri_set() and cpupri_init() can never be used without
> CONFIG_SMP.
> 

Acked-by: Steven Rostedt <rostedt@...dmis.org>

-- Steve

> Signed-off-by: pang.xunlei <pang.xunlei@...aro.org>
> ---
>  kernel/sched/cpupri.h |    3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/kernel/sched/cpupri.h b/kernel/sched/cpupri.h
> index 6b03334..63cbb9c 100644
> --- a/kernel/sched/cpupri.h
> +++ b/kernel/sched/cpupri.h
> @@ -26,9 +26,6 @@ int  cpupri_find(struct cpupri *cp,
>  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)
>  #endif
>  
>  #endif /* _LINUX_CPUPRI_H */

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