From: netz.kernel@gmail•com (Marty Plummer)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 3/7] Make Hi3620 explicit, remove wildcards
Date: Thu, 8 Sep 2016 12:23:42 -0500 [thread overview]
Message-ID: <20160908172346.27506-3-netz.kernel@gmail.com> (raw)
In-Reply-To: <20160908172346.27506-1-netz.kernel@gmail.com>
This is a preparatory series for adding the ARMv5/v6 hi3520 SoCs.
Assumptions were made when adding hi3620 that don't hold water in
light of adding support for the hi3520 SoC. Fix the issue by renaming
config options and other namespaces to avoid collisions with the new
work.
Only internal APIs are modified with this series.
Signed-off-by: Marty Plummer <netz.kernel@gmail•com>
---
arch/arm/configs/hisi_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/configs/hisi_defconfig b/arch/arm/configs/hisi_defconfig
index b2e340b..14c8da6 100644
--- a/arch/arm/configs/hisi_defconfig
+++ b/arch/arm/configs/hisi_defconfig
@@ -4,7 +4,7 @@ CONFIG_HIGH_RES_TIMERS=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_RD_LZMA=y
CONFIG_ARCH_HISI=y
-CONFIG_ARCH_HI3xxx=y
+CONFIG_ARCH_HI3620=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_CMDLINE_PARTITION=y
CONFIG_ARCH_HIX5HD2=y
--
2.9.3
next prev parent reply other threads:[~2016-09-08 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 17:23 [RFC 1/7] Make Hi3620 explicit, remove wildcards Marty Plummer
2016-09-08 17:23 ` [RFC 2/7] " Marty Plummer
2016-09-08 17:50 ` Jason Cooper
2016-09-08 17:23 ` Marty Plummer [this message]
2016-09-08 17:23 ` [RFC 4/7] " Marty Plummer
2016-09-08 17:23 ` [RFC 5/7] " Marty Plummer
2016-09-08 17:23 ` [RFC 6/7] " Marty Plummer
2016-09-08 17:23 ` [RFC 7/7] " Marty Plummer
2016-09-08 17:54 ` Jason Cooper
2016-09-08 18:04 ` Marty Plummer
2016-09-08 17:47 ` [RFC 1/7] " Jason Cooper
2016-09-08 17:55 ` Marty Plummer
2016-09-08 18:10 ` Jason Cooper
2016-09-08 19:46 ` Andrew Lunn
2016-09-08 20:05 ` Arnd Bergmann
2016-09-08 20:12 ` Marty Plummer
2016-09-08 20:22 ` 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=20160908172346.27506-3-netz.kernel@gmail.com \
--to=netz.kernel@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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