From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/7] Make Hi3620 explicit, remove wildcards
Date: Thu, 8 Sep 2016 17:50:36 +0000 [thread overview]
Message-ID: <20160908175036.GD12916@io.lakedaemon.net> (raw)
In-Reply-To: <20160908172346.27506-2-netz.kernel@gmail.com>
On Thu, Sep 08, 2016 at 12:23:41PM -0500, Marty Plummer wrote:
> 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/boot/dts/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
A quick trick for figuring out the preferred Subject line format for a
subsystem is to do:
$ git log --oneline --no-merges -- arch/arm/boot/dts/
thx,
Jason.
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index faacd52..7ffd3a3 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -154,7 +154,7 @@ dtb-$(CONFIG_ARCH_EXYNOS5) += \
> exynos5440-sd5v1.dtb \
> exynos5440-ssdk5440.dtb \
> exynos5800-peach-pi.dtb
> -dtb-$(CONFIG_ARCH_HI3xxx) += \
> +dtb-$(CONFIG_ARCH_HI3620) += \
> hi3620-hi4511.dtb
> dtb-$(CONFIG_ARCH_HIGHBANK) += \
> highbank.dtb \
> --
> 2.9.3
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-09-08 17:50 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 [this message]
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
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=20160908175036.GD12916@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.