From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Sangwook Lee <sangwook.lee@linaro.org>, Chris Ball <cjb@laptop.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linaro-dev@linaro.org, linux-mmc@vger.kernel.org
Subject: Build breakage in sdhci-s3c
Date: Fri, 2 Dec 2011 11:58:07 +0000 [thread overview]
Message-ID: <20111202115807.GJ8245@opensource.wolfsonmicro.com> (raw)
The mmc and therefore -next currently fail to build on Samsung platforms
due to commit 666b6a (mmc: sdhci-s3c: Add pm_caps into SD/MMC host)
which added use of a new field pm_caps in the platform data without
actually adding that field to the struct. I guess there's a separate
patch floating about somewhere which adds the field but it's not in
-next and both commits should be going in via the same tree to avoid
bisection breakage - ideally both the field and its use should be added
as part of a single commit.
next reply other threads:[~2011-12-02 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 11:58 Mark Brown [this message]
2011-12-02 12:59 ` Build breakage in sdhci-s3c Sangwook Lee
2011-12-02 13:04 ` Mark Brown
2011-12-02 13:11 ` Sangwook Lee
2011-12-03 9:25 ` Kukjin Kim
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=20111202115807.GJ8245@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=kgene.kim@samsung.com \
--cc=linaro-dev@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sangwook.lee@linaro.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.