From: tip-bot for Peter Zijlstra <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
peterz@infradead.org, tglx@linutronix.de
Subject: [tip:core/locking] locking: Move mcs_spinlock.h into kernel/ locking/
Date: Tue, 11 Mar 2014 05:40:48 -0700 [thread overview]
Message-ID: <tip-byirmpamgr7h25m5kyavwpzx@git.kernel.org> (raw)
Commit-ID: c9122da1e2d29bd6a1475a0d1ce2aa6ac6ea25fa
Gitweb: http://git.kernel.org/tip/c9122da1e2d29bd6a1475a0d1ce2aa6ac6ea25fa
Author: Peter Zijlstra <peterz@infradead.org>
AuthorDate: Mon, 3 Feb 2014 13:32:16 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 11 Mar 2014 12:14:52 +0100
locking: Move mcs_spinlock.h into kernel/locking/
The mcs_spinlock code is not meant (or suitable) as a generic locking
primitive, therefore take it away from the normal includes and place
it in kernel/locking/.
This way the locking primitives implemented there can use it as part
of their implementation but we do not risk it getting used
inapropriately.
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/n/tip-byirmpamgr7h25m5kyavwpzx@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
{include/linux => kernel/locking}/mcs_spinlock.h | 0
kernel/locking/mutex.c | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mcs_spinlock.h b/kernel/locking/mcs_spinlock.h
similarity index 100%
rename from include/linux/mcs_spinlock.h
rename to kernel/locking/mcs_spinlock.h
diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
index 45fe1b5..4f408be 100644
--- a/kernel/locking/mutex.c
+++ b/kernel/locking/mutex.c
@@ -25,7 +25,7 @@
#include <linux/spinlock.h>
#include <linux/interrupt.h>
#include <linux/debug_locks.h>
-#include <linux/mcs_spinlock.h>
+#include "mcs_spinlock.h"
/*
* In the DEBUG case we are using the "NULL fastpath" for mutexes,
reply other threads:[~2014-03-11 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-byirmpamgr7h25m5kyavwpzx@git.kernel.org \
--to=tipbot@zytor.com \
--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 \
/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