From: Greg KH <gregkh@linuxfoundation.org>
To: Sowjanya Komatineni <skomatineni@nvidia.com>
Cc: Sasha Levin <sashal@kernel.org>,
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, stable@vger.kernel.org
Subject: Re: [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection
Date: Wed, 13 May 2020 11:37:51 +0200 [thread overview]
Message-ID: <20200513093751.GA831267@kroah.com> (raw)
In-Reply-To: <20200425070408.GB2042217@kroah.com>
On Sat, Apr 25, 2020 at 09:04:08AM +0200, Greg KH wrote:
> On Fri, Apr 24, 2020 at 07:42:16PM -0700, Sowjanya Komatineni wrote:
> >
> > On 4/24/20 6:45 PM, Sasha Levin wrote:
> > > External email: Use caution opening links or attachments
> > >
> > >
> > > On Fri, Apr 24, 2020 at 01:06:04PM -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
> > >
> > > What regression do these patches fix?
> > >
> > This isn't a regression as we don't have any known failures as of today with
> > the specific mmc devices we are using on our platforms.
>
> Have you read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> ?
>
> > But this patch fixes a long outstanding bug for sdhci-tegra to handle long
> > busy wait for mmc command operations that may take longer than host max busy
> > timeout. So, this is something that's missing from the beginning and good to
> > have.
>
> So it's a new feature?
>
Dropped from my queues due to lack of response.
greg k-h
prev parent reply other threads:[~2020-05-13 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 20:06 [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection Sowjanya Komatineni
2020-04-24 20:06 ` [PATCH 5.4.33 1/2] sdhci: tegra: Implement Tegra specific set_timeout callback Sowjanya Komatineni
2020-04-24 20:06 ` [PATCH 5.4.33 2/2] sdhci: tegra: Enable MMC_CAP_WAIT_WHILE_BUSY host capability Sowjanya Komatineni
2020-04-25 1:45 ` [PATCH 5.4.33 0/2] Fix for long operation cmds busy detection Sasha Levin
2020-04-25 2:42 ` Sowjanya Komatineni
2020-04-25 7:04 ` Greg KH
2020-05-13 9:37 ` Greg KH [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=20200513093751.GA831267@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=sashal@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).