From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] arm64: add Kconfig entry for LG1K SoC family
Date: Wed, 13 Apr 2016 15:15:07 -0700 [thread overview]
Message-ID: <20160413221507.GA19945@localhost> (raw)
In-Reply-To: <1460375687-2375-2-git-send-email-chanho.min@lge.com>
On Mon, Apr 11, 2016 at 08:54:44PM +0900, Chanho Min wrote:
> This patch introduces ARCH_LG1K to enable LG Electronics's LG1K SoC
> family in Kconfig.
>
> Signed-off-by: Chanho Min <chanho.min@lge.com>
> ---
> Changes for v2:
> - None
> Changes for v3:
> - None
> ---
> arch/arm64/Kconfig.platforms | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 21074f6..b002bba 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -141,4 +141,8 @@ config ARCH_ZYNQMP
> help
> This enables support for Xilinx ZynqMP Family
>
> +config ARCH_LG1K
> + bool "LG Electronics LG1K SoC Family"
> + help
> + This enables support for LG Electronics LG1K SoC Family
> endmenu
Did you see that the list of machine entries here are listed alphabetically?
They are, and you're appending out of order here. I've moved it for you but
please pay attention to these kind of things.
-Olof
next prev parent reply other threads:[~2016-04-13 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 11:54 [PATCH v3 0/4] ARM64:SoC add a new platform, LG Electronics's lg1k Chanho Min
2016-04-11 11:54 ` [PATCH v3 1/4] arm64: add Kconfig entry for LG1K SoC family Chanho Min
2016-04-13 22:15 ` Olof Johansson [this message]
2016-04-11 11:54 ` [PATCH v3 2/4] arm64: defconfig: enable ARCH_LG1K Chanho Min
2016-04-13 22:15 ` Olof Johansson
2016-04-11 11:54 ` [PATCH v3 3/4] arm64: dts: Add dts files for LG Electronics's lg1312 SoC Chanho Min
2016-04-13 22:16 ` Olof Johansson
2016-04-11 11:54 ` [PATCH v3 4/4] MAINTAINERS: add myself as ARM/LG1K maintainer Chanho Min
2016-04-13 22:17 ` Olof Johansson
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=20160413221507.GA19945@localhost \
--to=olof@lixom.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 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).