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:05:13 +0200 [thread overview]
Message-ID: <4234280.g2uciTKcvR@wuerfel> (raw)
In-Reply-To: <20160908172346.27506-1-netz.kernel@gmail.com>
On Thursday, September 8, 2016 12:23:40 PM CEST Marty Plummer wrote:
> arch/arm/Kconfig.debug | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index a9693b6..9094ca6 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -280,7 +280,7 @@ choice
>
> config DEBUG_HI3620_UART
> bool "Hisilicon HI3620 Debug UART"
> - depends on ARCH_HI3xxx
> + depends on ARCH_HI3620
> select DEBUG_UART_PL01X
> help
> Say Y here if you want kernel low-level debugging support
>
While patches should normally be split up into per-subsystem
changes, they also have to be done in an 'atomic' way:
applying just the first patch without the second one must
not introduce a regression.
In this case, I'd suggest simply doing a larger patch for
the global rename to collect 'Acked-by's and send that through
the arm-soc tree.
If you get in a similar situation with more complex changes,
you should come up with a way to do it independently. Here
you would first have to introduce a CONFIG_ARCH_HI3620
symbol in one patch and make that always selected at
the same time as CONFIG_ARCH_HI3xxx, then change all users
of that symbol, and finally remove the original.
Arnd
next prev parent reply other threads:[~2016-09-08 20:05 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 [this message]
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=4234280.g2uciTKcvR@wuerfel \
--to=arnd@arndb$(echo .)de \
--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