From: Kevin Hilman <khilman@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Georgi Djakov <gdjakov@mm-sol.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [PATCH] mmc: sdhci-msm: Fix fallout from sdhci refactoring
Date: Tue, 10 Jun 2014 12:41:59 -0700 [thread overview]
Message-ID: <7hzjhko8l4.fsf@paris.lan> (raw)
In-Reply-To: <1402424839-25514-1-git-send-email-sboyd@codeaurora.org> (Stephen Boyd's message of "Tue, 10 Jun 2014 11:27:19 -0700")
Stephen Boyd <sboyd@codeaurora.org> writes:
> The sdhci core was refactored recently and some of those
> refactorings required changes in every sdhci platform driver.
> Those updates happened around the same time as when the msm
> driver was merged so the refactorings missed the msm driver.
> Hook in the basic library functions so that we can boot apq8074
> dragonboards again instead of crashing when we try to jump to
> NULL function pointers.
>
> Reported-by: Kevin Hilman <khilman@linaro.org>
> Cc: Georgi Djakov <gdjakov@mm-sol.com>
> Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Tested-by: Kevin Hilman <khilman@linaro.org>
I verifed that this patch on top of next-20140610 gets the qcom
dragonboard booting again.
Kevin
next prev parent reply other threads:[~2014-06-10 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 18:27 [PATCH] mmc: sdhci-msm: Fix fallout from sdhci refactoring Stephen Boyd
2014-06-10 18:59 ` Kumar Gala
2014-06-10 19:39 ` Georgi Djakov
2014-06-10 19:41 ` Kevin Hilman [this message]
2014-06-12 8:59 ` Ulf Hansson
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=7hzjhko8l4.fsf@paris.lan \
--to=khilman@linaro.org \
--cc=chris@printf.net \
--cc=gdjakov@mm-sol.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sboyd@codeaurora.org \
--cc=ulf.hansson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox