From: Lukas Wunner <lukas@wunner.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Andreas Noever <andreas.noever@gmail.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] thunderbolt: Compile on x86 only
Date: Fri, 18 Nov 2016 09:22:59 +0100 [thread overview]
Message-ID: <7dfda728d3ee8a33c80c49b224da7359c6015eea.1479456179.git.lukas@wunner.de> (raw)
In-Reply-To: <cover.1479456179.git.lukas@wunner.de>
So far Thunderbolt is (unfortunately) an Intel proprietary technology
that is only available on x86, so compiling on other arches is pointless
except for testing purposes. Amend Kconfig accordingly.
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Cc: Andreas Noever <andreas.noever@gmail.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
drivers/thunderbolt/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/thunderbolt/Kconfig b/drivers/thunderbolt/Kconfig
index de5d27e..d35db16 100644
--- a/drivers/thunderbolt/Kconfig
+++ b/drivers/thunderbolt/Kconfig
@@ -1,6 +1,7 @@
menuconfig THUNDERBOLT
tristate "Thunderbolt support for Apple devices"
depends on PCI
+ depends on X86 || COMPILE_TEST
select APPLE_PROPERTIES if EFI_STUB && X86
select CRC32
help
--
2.10.1
next prev parent reply other threads:[~2016-11-18 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 8:22 [PATCH 0/2] Thunderbolt Kbuild fixes Lukas Wunner
2016-11-18 8:22 ` Lukas Wunner [this message]
2016-11-18 9:05 ` [tip:efi/core] thunderbolt: Compile on x86 only tip-bot for Lukas Wunner
2016-11-18 8:22 ` [PATCH 1/2] thunderbolt, efi: Fix Kconfig dependencies harder Lukas Wunner
2016-11-18 9:05 ` [tip:efi/core] " tip-bot for Lukas Wunner
2016-11-18 8:30 ` [PATCH 0/2] Thunderbolt Kbuild fixes Arnd Bergmann
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=7dfda728d3ee8a33c80c49b224da7359c6015eea.1479456179.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=andreas.noever@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®