From: Alexei Colin <acolin@isi.edu>
To: Alexandre Bounine <alex.bou9@gmail.com>,
Matt Porter <mporter@kernel.crashing.org>
Cc: Alexei Colin <acolin@isi.edu>,
Andrew Morton <akpm@linux-foundation.org>,
John Paul Walters <jwalters@isi.edu>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/6] rapidio: define top Kconfig menu in driver subtree
Date: Mon, 30 Jul 2018 18:50:29 -0400 [thread overview]
Message-ID: <20180730225035.28365-2-acolin@isi.edu> (raw)
In-Reply-To: <20180730225035.28365-1-acolin@isi.edu>
The top-level Kconfig entry for RapidIO subsystem is currently
duplicated in several architecture-specific Kconfigs. This
commit re-defines it in the driver subtree, and subsequent
commits, one per architecture, will remove the duplicated
definitions from respective per-architecture Kconfigs.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: John Paul Walters <jwalters@isi.edu>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Alexei Colin <acolin@isi.edu>
---
drivers/rapidio/Kconfig | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/drivers/rapidio/Kconfig b/drivers/rapidio/Kconfig
index d6d2f20c4597..98e301847584 100644
--- a/drivers/rapidio/Kconfig
+++ b/drivers/rapidio/Kconfig
@@ -1,6 +1,21 @@
#
# RapidIO configuration
#
+
+config HAS_RAPIDIO
+ bool
+ default n
+
+config RAPIDIO
+ tristate "RapidIO support"
+ depends on HAS_RAPIDIO || PCI
+ help
+ This feature enables support for RapidIO high-performance
+ packet-switched interconnect.
+
+ If you say Y here, the kernel will include drivers and
+ infrastructure code to support RapidIO interconnect devices.
+
source "drivers/rapidio/devices/Kconfig"
config RAPIDIO_DISC_TIMEOUT
--
2.18.0
next prev parent reply other threads:[~2018-07-30 22:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 22:50 [PATCH 0/6] rapidio: move Kconfig menu definition to subsystem Alexei Colin
2018-07-30 22:50 ` Alexei Colin [this message]
2018-07-30 22:50 ` [PATCH 2/6] x86: factor out RapidIO Kconfig menu Alexei Colin
2018-07-30 22:55 ` [PATCH 2/6] x86: factor out RapidIO Kconfig menu; Thomas Gleixner
2018-07-31 14:30 ` Alex Bounine
2018-07-30 22:50 ` [PATCH 3/6] powerpc: factor out RapidIO Kconfig menu entry Alexei Colin
2018-07-31 9:45 ` Michael Ellerman
2018-07-30 22:50 ` [PATCH 4/6] mips: factor out RapidIO Kconfig entry Alexei Colin
2018-07-31 8:13 ` Alexander Sverdlin
2018-07-30 22:50 ` [PATCH 5/6] arm: enable RapidIO menu in Kconfig Alexei Colin
2018-07-31 12:04 ` Christoph Hellwig
2018-07-31 12:43 ` Alex Bounine
2018-07-31 12:48 ` Russell King - ARM Linux
2018-07-31 13:15 ` Alex Bounine
2018-07-30 22:50 ` [PATCH 6/6] arm64: " Alexei Colin
2018-07-31 8:41 ` Will Deacon
2018-07-31 12:54 ` Alex Bounine
2018-07-31 15:52 ` Russell King - ARM Linux
2018-07-31 17:59 ` Alex Bounine
2018-07-31 18:18 ` Russell King - ARM Linux
2018-07-31 20:01 ` Alex Bounine
2018-08-01 10:38 ` Russell King - ARM Linux
2018-08-01 13:54 ` Alexei Colin
2018-08-01 15:14 ` Alex Bounine
2018-07-31 20:29 ` Alex Bounine
2018-07-31 20:46 ` Alexei Colin
2018-08-01 13:57 ` Alex Bounine
2018-08-01 9:10 ` Will Deacon
2018-07-30 22:59 ` [PATCH 0/6] rapidio: move Kconfig menu definition to subsystem Russell King - ARM Linux
2018-07-31 1:08 ` Randy Dunlap
2018-07-31 14:26 ` Alex Bounine
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=20180730225035.28365-2-acolin@isi.edu \
--to=acolin@isi.edu \
--cc=akpm@linux-foundation.org \
--cc=alex.bou9@gmail.com \
--cc=jwalters@isi.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@kernel.crashing.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