From: Saeed Bishara <saeed@marvell.com>
To: Chris Ball <cjb@laptop.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: RE: [PATCH] mmc: Add architecture dependency for Marvell SoC controller
Date: Wed, 15 Sep 2010 12:55:33 +0300 [thread overview]
Message-ID: <FCBE654890C0334289D0AD3AF4EF009FD18EE74AA8@IL-MB01.marvell.com> (raw)
In-Reply-To: <20100915094006.GA21620@sirena.org.uk>
>-----Original Message-----
>From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
>Sent: Wednesday, September 15, 2010 11:40 AM
>To: Chris Ball
>Cc: Saeed Bishara; Andrew Morton; linux-mmc@vger.kernel.org;
>linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] mmc: Add architecture dependency for
>Marvell SoC controller
>
>On Tue, Sep 14, 2010 at 08:05:49PM +0100, Chris Ball wrote:
>
>> This is fine with me. Saeed, please can you ACK the choice of
>> platforms if you agree?
>
>If the list of platforms is wrong we should probably also improve the
>help text :)
I think the PLAT_PXA it too general, maybe you better specify the exact ARCH (ARCH_MMP).
saeed
>
next prev parent reply other threads:[~2010-09-15 11:01 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
2010-09-14 19:05 ` Chris Ball
2010-09-15 9:40 ` Mark Brown
2010-09-15 9:55 ` Saeed Bishara [this message]
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=FCBE654890C0334289D0AD3AF4EF009FD18EE74AA8@IL-MB01.marvell.com \
--to=saeed@marvell.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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.