From: Kevin Hao <haokexin@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc <linuxppc-dev@lists.ozlabs.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 2/5] jump_label: also include linux/atomic.h when jump label is enabled
Date: Sun, 25 Aug 2013 15:15:49 +0800 [thread overview]
Message-ID: <1377414952-15995-3-git-send-email-haokexin@gmail.com> (raw)
In-Reply-To: <1377414952-15995-1-git-send-email-haokexin@gmail.com>
The struct static_key will have a atomic_t type member no matter
whether jump label is enabled or not. We would include linux/atomic.h
when jump label is not enabled. But it also does make sense to include
this header file when jump label is enabled.
Signed-off-by: Kevin Hao <haokexin@gmail.com>
---
include/linux/jump_label_base.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/jump_label_base.h b/include/linux/jump_label_base.h
index 20df08f..d5c8f4b 100644
--- a/include/linux/jump_label_base.h
+++ b/include/linux/jump_label_base.h
@@ -5,6 +5,8 @@
#include <linux/types.h>
#include <linux/compiler.h>
+#include <linux/atomic.h>
+
#if defined(CC_HAVE_ASM_GOTO) && defined(CONFIG_JUMP_LABEL)
struct static_key {
@@ -77,8 +79,6 @@ extern void jump_label_apply_nops(struct module *mod);
#else /* !HAVE_JUMP_LABEL */
-#include <linux/atomic.h>
-
struct static_key {
atomic_t enabled;
};
--
1.8.3.1
next prev parent reply other threads:[~2013-08-25 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 7:15 [PATCH 0/5] powerpc: use jump label for cpu/mmu_has_feature Kevin Hao
2013-08-25 7:15 ` [PATCH 1/5] jump_label: factor out the base part of jump_label.h to a separate file Kevin Hao
2013-08-30 16:37 ` Radim Krčmář
2013-09-02 2:23 ` Kevin Hao
2013-08-25 7:15 ` Kevin Hao [this message]
2013-08-25 7:15 ` [PATCH 3/5] powerpc: move the cpu_has_feature " Kevin Hao
2013-08-25 7:15 ` [PATCH 4/5] powerpc: use the jump label for cpu_has_feature Kevin Hao
2013-08-25 7:15 ` [PATCH 5/5] powerpc: use jump label for mmu_has_feature Kevin Hao
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=1377414952-15995-3-git-send-email-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).