From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm64: Initial defconfig for APM X-Gene SOC family
Date: Sat, 20 Apr 2013 09:35:14 +0200 [thread overview]
Message-ID: <2165570.9Zy5vrhoIa@wuerfel> (raw)
In-Reply-To: <1366442131-26094-3-git-send-email-vkale@apm.com>
On Saturday 20 April 2013 12:45:29 Vinayak Kale wrote:
> This patch adds initial defconfig for APM X-Gene SOC family.
>
> Signed-off-by: Kumar Sankaran <ksankaran@apm.com>
> Signed-off-by: Loc Ho <lho@apm.com>
> Signed-off-by: Feng Kan <fkan@apm.com>
> ---
> arch/arm64/configs/xgene_defconfig | 93 ++++++++++++++++++++++++++++++++++++
> 1 files changed, 93 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm64/configs/xgene_defconfig
Could you modify the regular defconfig to enable everything you need instead
of adding another one? Since all the code is interoperable, I think we
should not need a defconfig per soc.
Arnd
next prev parent reply other threads:[~2013-04-20 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 7:15 [PATCH 0/4] arm64: Initial patch-set for APM X-Gene SOC family Vinayak Kale
2013-04-20 7:15 ` [PATCH 1/4] arm64: Add Kconfig option " Vinayak Kale
2013-04-20 7:15 ` [PATCH 2/4] arm64: Initial defconfig " Vinayak Kale
2013-04-20 7:35 ` Arnd Bergmann [this message]
2013-04-20 9:31 ` Vinayak Kale
2013-04-20 10:27 ` Arnd Bergmann
2013-04-22 17:31 ` Catalin Marinas
2013-04-22 19:25 ` Arnd Bergmann
2013-04-20 7:15 ` [PATCH 3/4] arm64: Add defines for APM ARMv8 implementation Vinayak Kale
2013-04-20 7:15 ` [PATCH 4/4] arm64: Add initial DTS for APM X-Gene Storm SOC and APM Mustang board Vinayak Kale
2013-04-20 7:39 ` Arnd Bergmann
2013-04-20 9:19 ` Vinayak Kale
2013-04-22 11:14 ` Mark Rutland
2013-04-22 12:23 ` Vinayak Kale
2013-04-22 12:59 ` Mark Rutland
2013-04-22 13:27 ` Vinayak Kale
2013-04-22 20:59 ` Rob Herring
2013-04-23 5:27 ` Vinayak Kale
2013-04-23 18:11 ` Olof Johansson
2013-04-24 6:21 ` Vinayak Kale
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=2165570.9Zy5vrhoIa@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