From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: faiz_abbas@ti.com, ulf.hansson@linaro.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mmc: sdhci: Update the tuning failed messages to pr_debug" failed to apply to 4.9-stable tree
Date: Wed, 1 Jan 2020 20:26:00 -0500 [thread overview]
Message-ID: <20200102012600.GG16372@sasha-vm> (raw)
In-Reply-To: <1577635521151247@kroah.com>
On Sun, Dec 29, 2019 at 05:05:21PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 2c92dd20304f505b6ef43d206fff21bda8f1f0ae Mon Sep 17 00:00:00 2001
>From: Faiz Abbas <faiz_abbas@ti.com>
>Date: Fri, 6 Dec 2019 17:13:26 +0530
>Subject: [PATCH] mmc: sdhci: Update the tuning failed messages to pr_debug
> level
>
>Tuning support in DDR50 speed mode was added in SD Specifications Part1
>Physical Layer Specification v3.01. Its not possible to distinguish
>between v3.00 and v3.01 from the SCR and that is why since
>commit 4324f6de6d2e ("mmc: core: enable CMD19 tuning for DDR50 mode")
>tuning failures are ignored in DDR50 speed mode.
>
>Cards compatible with v3.00 don't respond to CMD19 in DDR50 and this
>error gets printed during enumeration and also if retune is triggered at
>any time during operation. Update the printk level to pr_debug so that
>these errors don't lead to false error reports.
>
>Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
>Cc: stable@vger.kernel.org # v4.4+
>Link: https://lore.kernel.org/r/20191206114326.15856-1-faiz_abbas@ti.com
>Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
After 4.9 sdhci_execute_tuning() got split up into multiple functions,
and the actual text in the message was changed. I've adjusted the patch
and queued it up for 4.9 and 4.4.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-01-02 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 16:05 FAILED: patch "[PATCH] mmc: sdhci: Update the tuning failed messages to pr_debug" failed to apply to 4.9-stable tree gregkh
2020-01-02 1:26 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 19:08 gregkh
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=20200102012600.GG16372@sasha-vm \
--to=sashal@kernel.org \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--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).