From: tip-bot for Avi Kivity <avi@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
tglx@linutronix.de, mingo@elte.hu, avi@redhat.com
Subject: [tip:x86/entry] x86: Fix user return notifier build
Date: Mon, 2 Nov 2009 10:12:48 GMT [thread overview]
Message-ID: <tip-7a041097518a120f92af631a83db4d41e07ee51b@git.kernel.org> (raw)
In-Reply-To: <1256473485-23109-1-git-send-email-avi@redhat.com>
Commit-ID: 7a041097518a120f92af631a83db4d41e07ee51b
Gitweb: http://git.kernel.org/tip/7a041097518a120f92af631a83db4d41e07ee51b
Author: Avi Kivity <avi@redhat.com>
AuthorDate: Sun, 25 Oct 2009 14:24:45 +0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 25 Oct 2009 17:37:57 +0100
x86: Fix user return notifier build
When CONFIG_USER_RETURN_NOTIFIER is set, we need to link
kernel/user-return-notifier.o.
Signed-off-by: Avi Kivity <avi@redhat.com>
LKML-Reference: <1256473485-23109-1-git-send-email-avi@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/Makefile | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/Makefile b/kernel/Makefile
index b8d4cd8..0ae57a8 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -95,6 +95,7 @@ obj-$(CONFIG_RING_BUFFER) += trace/
obj-$(CONFIG_SMP) += sched_cpupri.o
obj-$(CONFIG_SLOW_WORK) += slow-work.o
obj-$(CONFIG_PERF_EVENTS) += perf_event.o
+obj-$(CONFIG_USER_RETURN_NOTIFIER) += user-return-notifier.o
ifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y)
# According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is
prev parent reply other threads:[~2009-11-02 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 12:24 [PATCH tip/x86/entry] " Avi Kivity
2009-10-25 16:38 ` Ingo Molnar
2009-10-25 16:43 ` Avi Kivity
2009-11-02 10:12 ` tip-bot for Avi Kivity [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-7a041097518a120f92af631a83db4d41e07ee51b@git.kernel.org \
--to=avi@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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