From: Chris Ball <cjb@laptop.org>
To: Olof Johansson <olof@lixom.net>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Tuomas Tynkkynen <ttynkkynen@nvidia.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH] mmc: core: Fixup Oops for SDIO shutdown
Date: Sun, 07 Jul 2013 18:25:04 +0100 [thread overview]
Message-ID: <868v1i1dvz.fsf@void.printf.net> (raw)
In-Reply-To: <CAOesGMiL-vY2O-WdiqcYOyNDvXz83PeDij+sijxrGTx-GLV+_w@mail.gmail.com> (Olof Johansson's message of "Sun, 7 Jul 2013 10:15:22 -0700")
Hi,
On Sun, Jul 07 2013, Olof Johansson wrote:
> On Tue, Jul 2, 2013 at 8:15 AM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 07/02/2013 04:53 AM, Ulf Hansson wrote:
>>> Commit "mmc: core: Handle card shutdown from mmc_bus" introduced an
>>> Oops in the shutdown sequence for SDIO.
>>>
>>> The drv pointer, does not exist for SDIO since the probing of the SDIO
>>> card from the mmc_bus perspective is expected to fail by returning
>>> -ENODEV.
>>>
>>> This patch adds the proper check for the pointer before calling it.
>>
>> Tested-by: Stephen Warren <swarren@nvidia.com>
>
> Acked-by: Olof Johansson <olof@lixom.net>
>
> Chris, I hit this on the 0705 linux-next. Can you pick up this patch
> soonish please? Thanks!
Sorry for the delay -- I merged this on Friday, so it'll be in
tonight's -next.
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
next prev parent reply other threads:[~2013-07-07 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:53 [PATCH] mmc: core: Fixup Oops for SDIO shutdown Ulf Hansson
2013-07-02 10:58 ` Jaehoon Chung
2013-07-02 10:58 ` Tuomas Tynkkynen
2013-07-02 15:15 ` Stephen Warren
2013-07-07 17:15 ` Olof Johansson
2013-07-07 17:25 ` Chris Ball [this message]
2013-07-07 17:55 ` Olof Johansson
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=868v1i1dvz.fsf@void.printf.net \
--to=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@wwwdotorg.org \
--cc=ttynkkynen@nvidia.com \
--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 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.