From: tip-bot for Mark Brown <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: broonie@kernel.org, linux-kernel@vger.kernel.org, efault@gmx.de,
peterz@infradead.org, hpa@zytor.com,
torvalds@linux-foundation.org, mingo@kernel.org,
tglx@linutronix.de
Subject: [tip:sched/urgent] sched/core: Fix build paravirt build on arm and arm64
Date: Fri, 24 Feb 2017 01:19:38 -0800 [thread overview]
Message-ID: <tip-d31c710a3f3ea69b017002a109a1e2a1750054f5@git.kernel.org> (raw)
In-Reply-To: <20170217110607.31264-1-broonie@kernel.org>
Commit-ID: d31c710a3f3ea69b017002a109a1e2a1750054f5
Gitweb: http://git.kernel.org/tip/d31c710a3f3ea69b017002a109a1e2a1750054f5
Author: Mark Brown <broonie@kernel.org>
AuthorDate: Fri, 17 Feb 2017 11:06:07 +0000
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 24 Feb 2017 09:30:54 +0100
sched/core: Fix build paravirt build on arm and arm64
Commit:
004172bdad64432: ("sched/core: Remove unnecessary #include headers")
... in current -next removed the inclusion of asm/paravirt.h which
is used to get declarations of paravirt_steal_rq_enabled and
paravirt_steal_clock.
It is implicitly included on but not on arm and arm64 breaking the build
if paravirtualization is used. Since things from that header are used
directly fix the build by putting the direct inclusion back.
Signed-off-by: Mark Brown <broonie@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/20170217110607.31264-1-broonie@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
kernel/sched/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index e01bd80..b692d6c 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -23,6 +23,9 @@
#include <asm/switch_to.h>
#include <asm/tlb.h>
+#ifdef CONFIG_PARAVIRT
+#include <asm/paravirt.h>
+#endif
#include "sched.h"
#include "../workqueue_internal.h"
prev parent reply other threads:[~2017-02-24 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 11:06 [PATCH] " Mark Brown
2017-02-24 9:19 ` tip-bot for Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tip-d31c710a3f3ea69b017002a109a1e2a1750054f5@git.kernel.org \
--to=tipbot@zytor.com \
--cc=broonie@kernel.org \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome