All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Douglas Anderson <dianders@chromium.org>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Shawn Lin <shawn.lin@rock-chips.com>,
	Heiko Stuebner <heiko@sntech.de>,
	kevin@archlinuxarm.org, Alexandru Stan <amstan@chromium.org>,
	Ziyuan Xu <xzy.xu@rock-chips.com>,
	"# 4.0+" <stable@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: dw_mmc: Don't allow Runtime PM for SDIO cards
Date: Wed, 19 Apr 2017 10:55:05 -0700	[thread overview]
Message-ID: <20170419175504.GA91276@google.com> (raw)
In-Reply-To: <CAPDyKFoK+zv+dY1+qrWg10kBE9S7enDkxbKQTy=XejsKmq+Z3A@mail.gmail.com>

I'm a little late as this already landed (and I trusted Doug was
handling this just fine), but anyway:

On Tue, Apr 18, 2017 at 09:15:29PM +0200, Ulf Hansson wrote:
> Thanks, applied for fixes!

Yes, thanks :)

FWIW:

Tested-by: Brian Norris <briannorris@chromium.org>

Also, for some reason the eMMC crashes are now harder to reproduce.
Perhaps I was just (un)lucky the first few times I tested. Maybe it's an
existing issue and hasn't gotten much worse, except for possibly the
additional churn that runtime PM gives it.

But the SDIO/Wifi issues were definitely the primary thing that prompted
my original report, so I'm much happier now.

Brian

      reply	other threads:[~2017-04-19 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170411225640epcas2p44720be993462ea13ae585bbb7e60315d@epcas2p4.samsung.com>
2017-04-11 22:55 ` [PATCH] mmc: dw_mmc: Don't allow Runtime PM for SDIO cards Douglas Anderson
2017-04-12  5:01   ` Jaehoon Chung
2017-04-13  8:33   ` Shawn Lin
2017-04-13  9:32   ` Ulf Hansson
2017-04-13 15:05     ` Doug Anderson
2017-04-18 19:15   ` Ulf Hansson
2017-04-19 17:55     ` Brian Norris [this message]

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=20170419175504.GA91276@google.com \
    --to=briannorris@chromium.org \
    --cc=amstan@chromium.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=jh80.chung@samsung.com \
    --cc=kevin@archlinuxarm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=xzy.xu@rock-chips.com \
    /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.