From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/7] Make Hi3620 explicit, remove wildcards
Date: Thu, 08 Sep 2016 22:22:14 +0200 [thread overview]
Message-ID: <6260903.qUKuQuTBEX@wuerfel> (raw)
In-Reply-To: <df45ed73-0f7a-89d0-7cc5-5b6549f2b0f9@gmail.com>
On Thursday, September 8, 2016 3:12:26 PM CEST Marty Plummer wrote:
> So, in this case it should be one single patch? Geeze this is hella
> complicated to just get a name changed
Yes and yes. Sometimes it's easier to leave an slightly misleading
name than to change it. ;-)
If there is any relation between Hi3620 and Hi3520, we could also
decide to use the "HI3xxx" name for both after all, and just
change the Kconfig files like
config ARCH_HI3xxx
bool "Hisilicon Hi36xx family"
depends on ARCH_MULTI_V5 || ARCH_MULTI_V6 || ARCH_MULTI_V7
select CACHE_L2X0 if CPU_V7
select HAVE_ARM_SCU if SMP
...
config DEBUG_HI3520_UART
bool "Hisilicon HI3520 Debug UART"
depends on ARCH_HI3xxx
select DEBUG_UART_PL01X
help
Say Y here if you want kernel low-level debugging support
config DEBUG_HI3620_UART
bool "Hisilicon HI3620 Debug UART"
depends on ARCH_HI3xxx
select DEBUG_UART_PL01X
help
Say Y here if you want kernel low-level debugging support
Arnd
prev parent reply other threads:[~2016-09-08 20:22 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 ` [RFC 3/7] " Marty Plummer
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 [this message]
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=6260903.qUKuQuTBEX@wuerfel \
--to=arnd@arndb.de \
--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