From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mach-u300: do away with MMC config files
Date: Fri, 20 Jan 2012 11:09:23 +0000 [thread overview]
Message-ID: <20120120110923.GI1068@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1327057220-8300-1-git-send-email-linus.walleij@stericsson.com>
On Fri, Jan 20, 2012 at 12:00:20PM +0100, Linus Walleij wrote:
> static struct amba_device mmcsd_device = {
> .dev = {
> .init_name = "mmci", /* Fast device at 0x1000 offset */
> - .platform_data = NULL, /* Added later */
> + .platform_data = &mmcsd_platform_data,
This will certainly conflict with the set of AMBA/Primecell patches
I've just posted... the equivalent change is:
static AMBA_APB_DEVICE(mmcsd, "mmci", 0, U300_MMCSD_BASE,
- U300_MMCSD_IRQS, NULL);
+ U300_MMCSD_IRQS, &mmcsd_platform_data);
next prev parent reply other threads:[~2012-01-20 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 11:00 [PATCH] mach-u300: do away with MMC config files Linus Walleij
2012-01-20 11:09 ` Russell King - ARM Linux [this message]
2012-01-20 12:29 ` Linus Walleij
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=20120120110923.GI1068@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).