From: tip-bot for Randy Dunlap <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: rdunlap@infradead.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, hpa@zytor.com, tglx@linutronix.de
Subject: [tip:locking/core] mutex: Drop linkage.h from mutex.h
Date: Sun, 25 Feb 2018 06:06:50 -0800 [thread overview]
Message-ID: <tip-6ce5ae7977c89f2a09092954396a66c90e8213f2@git.kernel.org> (raw)
In-Reply-To: <582b3892-4e4c-06b2-a368-5c2d439de7fc@infradead.org>
Commit-ID: 6ce5ae7977c89f2a09092954396a66c90e8213f2
Gitweb: https://git.kernel.org/tip/6ce5ae7977c89f2a09092954396a66c90e8213f2
Author: Randy Dunlap <rdunlap@infradead.org>
AuthorDate: Sat, 24 Feb 2018 21:22:12 -0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Sun, 25 Feb 2018 15:00:46 +0100
mutex: Drop linkage.h from mutex.h
<linux/mutex.h> does not use nor need <linux/linkage.h>, so drop that
one header file from mutex.h.
<linux/mutex.h> is currently #included in around 1250 C source files
(oops, I didn't count other header files that #include it), making it
the 27th most-used header file.
Build tested on i386 and x86_64 * (allnoconfig, tiny.config, defconfig,
allyesconfig, and allmodconfig) and x64_64 allmodconfig + SMP=disabled.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lkml.kernel.org/r/582b3892-4e4c-06b2-a368-5c2d439de7fc@infradead.org
---
include/linux/mutex.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/mutex.h b/include/linux/mutex.h
index f25c13423bd4..9b7fe56692bd 100644
--- a/include/linux/mutex.h
+++ b/include/linux/mutex.h
@@ -14,7 +14,6 @@
#include <asm/current.h>
#include <linux/list.h>
#include <linux/spinlock_types.h>
-#include <linux/linkage.h>
#include <linux/lockdep.h>
#include <linux/atomic.h>
#include <asm/processor.h>
prev parent reply other threads:[~2018-02-25 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 5:22 [PATCH] headers: linux/mutex.h: drop linkage.h Randy Dunlap
2018-02-25 14:06 ` tip-bot for Randy Dunlap [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-6ce5ae7977c89f2a09092954396a66c90e8213f2@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=rdunlap@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
all inboxes | Powered by JetHome®