From: "Emilio G. Cota" <cota@braap.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Matthew Wilcox <willy@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] semaphore: remove superfluous include of ftrace.h
Date: Sat, 13 Aug 2011 02:32:53 -0400 [thread overview]
Message-ID: <1313217173-32103-1-git-send-email-cota@braap.org> (raw)
From: "Emilio G. Cota" <cota@braap.org>
Inspecting the semaphore code I noticed the #include of ftrace.h,
which wasn't there last time I checked (years ago). It was
added by commit "74f4e36 ftrace: stacktrace fix", which
was partially (and manually) reverted by "3e61e0c mmiotrace
broken in linux-next (8-bit writes only)".
Since 3e61e0c the include of ftrace.h has been superfluous;
remove it.
Signed-off-by: Emilio G. Cota <cota@braap.org>
---
kernel/semaphore.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/kernel/semaphore.c b/kernel/semaphore.c
index 94a62c0..4b63e1d 100644
--- a/kernel/semaphore.c
+++ b/kernel/semaphore.c
@@ -31,7 +31,6 @@
#include <linux/sched.h>
#include <linux/semaphore.h>
#include <linux/spinlock.h>
-#include <linux/ftrace.h>
static noinline void __down(struct semaphore *sem);
static noinline int __down_interruptible(struct semaphore *sem);
--
1.7.6
reply other threads:[~2011-08-13 6:33 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=1313217173-32103-1-git-send-email-cota@braap.org \
--to=cota@braap.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=willy@linux.intel.com \
/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
all inboxes | Powered by JetHome®