From: Anders Roxell <anders.roxell@linaro.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, linux-mmc@vger.kernel.org,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Faiz Abbas <faiz_abbas@ti.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH 5.5.12 0/5] mmc: Fix some busy detect problems
Date: Thu, 26 Mar 2020 11:51:44 +0100 [thread overview]
Message-ID: <CADYN=9JS0fcM-B5XR9fCHiQGP1i7RSh2zUtJA+BSASGctDkJJg@mail.gmail.com> (raw)
In-Reply-To: <20200326025132.GA4189@sasha-vm>
On Thu, 26 Mar 2020 at 03:51, Sasha Levin <sashal@kernel.org> wrote:
>
> On Tue, Mar 24, 2020 at 07:06:45PM +0100, Ulf Hansson wrote:
> >This series provides a couple of manually backported mmc changes that fixes some
> >busy detect issues, for a couple of mmc host drivers (sdhci-tegra|omap).
> >
> >Ulf Hansson (5):
> > mmc: core: Allow host controllers to require R1B for CMD6
> > mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
> > mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
> > mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
> > mmc: sdhci-tegra: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY
> >
> > drivers/mmc/core/core.c | 5 ++++-
> > drivers/mmc/core/mmc.c | 7 +++++--
> > drivers/mmc/core/mmc_ops.c | 8 +++++---
> > drivers/mmc/host/sdhci-omap.c | 3 +++
> > drivers/mmc/host/sdhci-tegra.c | 3 +++
> > include/linux/mmc/host.h | 1 +
> > 6 files changed, 21 insertions(+), 6 deletions(-)
>
> I've queued this, the 5.4, and the 4.19 series. Thanks!
Hi Sasha,
I've tested all three kernels, but replied to 5.5 and 5.4 with "Tested-by".
I did not reply "Tested-by" on 4.19 because I did not get a good result there.
I'm investigating why it did not boot. I'm not sure if you should
apply the patches
yet to 4.19, and if you do, please do not add my "Tested-by" on 4.19.
Cheers,
Anders
prev parent reply other threads:[~2020-03-26 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 18:06 [PATCH 5.5.12 0/5] mmc: Fix some busy detect problems Ulf Hansson
2020-03-24 18:06 ` [PATCH 5.5.12 1/5] mmc: core: Allow host controllers to require R1B for CMD6 Ulf Hansson
2020-03-24 18:06 ` [PATCH 5.5.12 2/5] mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard Ulf Hansson
2020-03-24 18:06 ` [PATCH 5.5.12 3/5] mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command Ulf Hansson
2020-03-24 18:06 ` [PATCH 5.5.12 4/5] mmc: sdhci-omap: Fix busy detection by enabling MMC_CAP_NEED_RSP_BUSY Ulf Hansson
2020-03-24 18:06 ` [PATCH 5.5.12 5/5] mmc: sdhci-tegra: " Ulf Hansson
2020-03-24 18:20 ` [PATCH 5.5.12 0/5] mmc: Fix some busy detect problems Anders Roxell
2020-03-26 2:51 ` Sasha Levin
2020-03-26 4:38 ` Naresh Kamboju
2020-03-26 10:51 ` Anders Roxell [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='CADYN=9JS0fcM-B5XR9fCHiQGP1i7RSh2zUtJA+BSASGctDkJJg@mail.gmail.com' \
--to=anders.roxell@linaro.org \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mmc@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=sashal@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).