From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Chris Ball <cjb@laptop.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: Add architecture dependency for Marvell SoC controller
Date: Mon, 13 Sep 2010 13:02:48 +0100 [thread overview]
Message-ID: <20100913120247.GJ16606@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201009131248.38501.arnd@arndb.de>
On Mon, Sep 13, 2010 at 12:48:38PM +0200, Arnd Bergmann wrote:
> I think we normally try to do the the other way round: in order to increase
> build coverage, try to enable all drivers on as many platforms as possible,
> just don't have them in the defconfig.
This is not the general pattern for on-CPU devices on the embedded SoCs,
for those we normally only offer the config option when building for a
system which could physically have the device. Looking at the existing
MMC host drivers you'll see this pattern is already heavily used there -
all the existing embedded controllers have similar dependencies.
> Do you get build errors on other platforms? If yes, there is probably
> a bug in the driver that should be fixed instead.
No, I didn't even try to build it - I saw that I was being offered a
device for a Marvell CPU when building for a non-Marvell CPU.
next prev parent reply other threads:[~2010-09-13 12:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 8:24 [PATCH] mmc: Add architecture dependency for Marvell SoC controller Mark Brown
2010-09-13 10:48 ` Arnd Bergmann
2010-09-13 12:02 ` Mark Brown [this message]
2010-09-14 19:05 ` Chris Ball
2010-09-15 9:40 ` Mark Brown
2010-09-15 9:55 ` Saeed Bishara
2010-09-15 11:00 ` Mark Brown
2010-09-15 10:06 ` Saeed Bishara
2010-09-15 11:20 ` Haojian Zhuang
2010-09-15 10:29 ` Saeed Bishara
2010-09-15 11:59 ` Haojian Zhuang
2010-09-15 20:59 ` Chris Ball
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=20100913120247.GJ16606@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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.