From: Randy Dunlap <rdunlap@infradead.org>
To: LKML <linux-kernel@vger.kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>
Cc: Olof Johansson <olof@lixom.net>, Nishanth Menon <nm@ti.com>,
Benjamin Fair <b-fair@ti.com>, Tony Lindgren <tony@atomide.com>,
Tero Kristo <t-kristo@ti.com>
Subject: [PATCH 2/2] soc: ti: move 2 driver config options into the TI SOC drivers menu
Date: Thu, 19 Sep 2019 15:33:37 -0700 [thread overview]
Message-ID: <ae4b494c-9723-1bc2-e471-e0e9f7df6e8f@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Move the AM654 and J721E SOC config options inside the "TI SOC drivers"
menu with the other TI SOC drivers.
Fixes: a869b7b30dac ("soc: ti: Add Support for AM654 SoC config option")
Fixes: cff377f7897a ("soc: ti: Add Support for J721E SoC config option")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Olof Johansson <olof@lixom.net>
Cc: Nishanth Menon <nm@ti.com>
Cc: Benjamin Fair <b-fair@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
---
drivers/soc/ti/Kconfig | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
--- lnx-53.orig/drivers/soc/ti/Kconfig
+++ lnx-53/drivers/soc/ti/Kconfig
@@ -1,4 +1,12 @@
# SPDX-License-Identifier: GPL-2.0-only
+
+# TI SOC drivers
+#
+menuconfig SOC_TI
+ bool "TI SOC drivers support"
+
+if SOC_TI
+
# 64-bit ARM SoCs from TI
if ARM64
@@ -14,17 +22,9 @@ config ARCH_K3_J721E_SOC
help
Enable support for TI's J721E SoC Family.
-endif
+endif # ARCH_K3
-endif
-
-#
-# TI SOC drivers
-#
-menuconfig SOC_TI
- bool "TI SOC drivers support"
-
-if SOC_TI
+endif # ARM64
config KEYSTONE_NAVIGATOR_QMSS
tristate "Keystone Queue Manager Subsystem"
next reply other threads:[~2019-09-19 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 22:33 Randy Dunlap [this message]
2019-09-21 20:46 ` [PATCH 2/2] soc: ti: move 2 driver config options into the TI SOC drivers menu Randy Dunlap
2019-09-23 0:05 ` santosh.shilimkar
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=ae4b494c-9723-1bc2-e471-e0e9f7df6e8f@infradead.org \
--to=rdunlap@infradead.org \
--cc=b-fair@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/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).