From: tip-bot for Peter Zijlstra <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com, hpa@zytor.com,
mingo@kernel.org, peterz@infradead.org, richard@nod.at,
tglx@linutronix.de
Subject: [tip:core/locking] x86, um: Add generic barrier.h
Date: Tue, 28 Jan 2014 11:25:12 -0800 [thread overview]
Message-ID: <tip-rcmiqb07nyuhtsnmanxlj3il@git.kernel.org> (raw)
Commit-ID: 673c36745c9f3100672853840b27e27638435e74
Gitweb: http://git.kernel.org/tip/673c36745c9f3100672853840b27e27638435e74
Author: Peter Zijlstra <peterz@infradead.org>
AuthorDate: Tue, 28 Jan 2014 15:12:36 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 28 Jan 2014 15:27:36 +0100
x86, um: Add generic barrier.h
It appears arch/um doesn't have any asm/barrier.h; cure this by
including the generic one. Since UM is !SMP the defaults are good
enough.
( The motivation are the latest MCS locking patches which use generic
barriers. )
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Cc: Jeff Dike <jdike@addtoit.com>
Cc: Richard Weinberger <richard@nod.at>
Link: http://lkml.kernel.org/n/tip-rcmiqb07nyuhtsnmanxlj3il@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/um/include/asm/Kbuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/um/include/asm/Kbuild b/arch/um/include/asm/Kbuild
index fdde187..fb3a6cc 100644
--- a/arch/um/include/asm/Kbuild
+++ b/arch/um/include/asm/Kbuild
@@ -4,3 +4,4 @@ generic-y += ftrace.h pci.h io.h param.h delay.h mutex.h current.h exec.h
generic-y += switch_to.h clkdev.h
generic-y += trace_clock.h
generic-y += preempt.h
+generic-y += barrier.h
next reply other threads:[~2014-01-28 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 19:25 tip-bot for Peter Zijlstra [this message]
2014-01-28 19:30 ` [tip:core/locking] x86, um: Add generic barrier.h Peter Zijlstra
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-rcmiqb07nyuhtsnmanxlj3il@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.