From: Greg KH <gregkh@linuxfoundation.org>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: adrian.hunter@intel.com, ulf.hansson@linaro.org,
baolin.wang@linaro.org, kstewart@linuxfoundation.org,
tglx@linutronix.de, bradleybolen@gmail.com,
thierry.reding@gmail.com, jonathanh@nvidia.com, anrao@nvidia.com,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection
Date: Thu, 23 Apr 2020 08:47:55 +0200 [thread overview]
Message-ID: <20200423064755.GA3491005@kroah.com> (raw)
In-Reply-To: <1587573149-30269-1-git-send-email-skomatineni@nvidia.com>
On Wed, Apr 22, 2020 at 09:32:27AM -0700, Sowjanya Komatineni wrote:
> This series is to backport the upstream patches that fixes busy detection
> for long operation mmc commands by implementing Tegra specific timeout
> callback to switch between finite and infinite HW busy detection wait
> modes.
>
>
> Sowjanya Komatineni (2):
> sdhci: tegra: Implement Tegra specific set_timeout callback
> sdhci: tegra: Enable MMC_CAP_WAIT_WHILE_BUSY host capability
>
> drivers/mmc/host/sdhci-tegra.c | 33 +++++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
Any specific reason you did not cc: the stable@vger list when asking for
stable patches to be merged?
next prev parent reply other threads:[~2020-04-23 6:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 16:32 [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection Sowjanya Komatineni
2020-04-22 16:32 ` [PATCH 5.4.33 1/2] sdhci: tegra: Implement Tegra specific set_timeout callback Sowjanya Komatineni
2020-04-22 16:32 ` [PATCH 5.4.33 2/2] sdhci: tegra: Enable MMC_CAP_WAIT_WHILE_BUSY host capability Sowjanya Komatineni
2020-04-23 6:47 ` Greg KH [this message]
2020-04-23 15:38 ` [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection Sowjanya Komatineni
2020-04-24 7:23 ` Ulf Hansson
2020-04-24 18:09 ` Sowjanya Komatineni
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 20:06 Sowjanya Komatineni
2020-04-25 1:45 ` Sasha Levin
2020-04-25 2:42 ` Sowjanya Komatineni
2020-04-25 7:04 ` Greg KH
2020-05-13 9:37 ` Greg KH
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=20200423064755.GA3491005@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adrian.hunter@intel.com \
--cc=anrao@nvidia.com \
--cc=baolin.wang@linaro.org \
--cc=bradleybolen@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox