From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/5] arm64: fpsimd: include <linux/init.h> in fpsimd.h
Date: Thu, 15 Feb 2018 15:29:31 +0000 [thread overview]
Message-ID: <1518708575-12284-2-git-send-email-will.deacon@arm.com> (raw)
In-Reply-To: <1518708575-12284-1-git-send-email-will.deacon@arm.com>
fpsimd.h uses the __init annotation, so pull in linux/init.h
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
arch/arm64/include/asm/fpsimd.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/include/asm/fpsimd.h b/arch/arm64/include/asm/fpsimd.h
index 8857a0f0d0f7..fc3527b985ca 100644
--- a/arch/arm64/include/asm/fpsimd.h
+++ b/arch/arm64/include/asm/fpsimd.h
@@ -22,6 +22,7 @@
#ifndef __ASSEMBLY__
#include <linux/cache.h>
+#include <linux/init.h>
#include <linux/stddef.h>
/*
--
2.1.4
next prev parent reply other threads:[~2018-02-15 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 15:29 [RFC PATCH 0/5] Rewrite asm-generic/bitops/atomic.h and use on arm64 Will Deacon
2018-02-15 15:29 ` Will Deacon [this message]
2018-02-15 15:29 ` [RFC PATCH 2/5] asm-generic: Avoid including linux/kernel.h in asm-generic/bug.h Will Deacon
2018-02-15 15:29 ` [RFC PATCH 3/5] asm-generic/bitops/atomic.h: Rewrite using atomic_fetch_* Will Deacon
2018-02-15 17:08 ` Peter Zijlstra
2018-02-15 18:20 ` Will Deacon
2018-02-16 10:21 ` Peter Zijlstra
2018-02-19 14:01 ` Will Deacon
2018-02-19 14:04 ` Peter Zijlstra
2018-02-16 10:35 ` Peter Zijlstra
2018-02-16 14:18 ` Peter Zijlstra
2018-02-19 14:01 ` Will Deacon
2018-02-19 14:05 ` Peter Zijlstra
2018-02-15 15:29 ` [RFC PATCH 4/5] arm64: Replace our atomic bitops implementation with asm-generic Will Deacon
2018-02-15 15:29 ` [RFC PATCH 5/5] arm64: bitops: Include <asm-generic/bitops/ext2-atomic-setbit.h> Will Deacon
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=1518708575-12284-2-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).