All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 22 Apr 2013 21:25:55 +0200	[thread overview]
Message-ID: <201304222125.55220.arnd@arndb.de> (raw)
In-Reply-To: <20130422173116.GD9602@arm.com>

On Monday 22 April 2013, Catalin Marinas wrote:
> That's good as we can get any automatic builds using defconfig to test
> all the platforms. The only issue I see is that as the number of SoCs
> grows, if you only need to select a single SoC you could end up with
> features enabled for other platforms.

I don't see that as a problem, as long as the defconfig just works for
everyone. Anyone building an embedded system can just disable the drivers
they don't need.

	Arnd

  reply	other threads:[~2013-04-22 19:25 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
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 [this message]
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=201304222125.55220.arnd@arndb.de \
    --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 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.