From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: stable@vger.kernel.org, "Ulf Hansson" <ulf.hansson@linaro.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Bean Huo" <beanhuo@micron.com>,
"Nishad Kamdar" <nishadkamdar@gmail.com>,
"Christian Löhle" <CLoehle@hyperstone.com>,
"open list:MULTIMEDIA CARD (MMC),
SECURE DIGITAL (SD) AND..." <linux-mmc@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
alcooperx@gmail.com, kdasu.kdev@gmail.com
Subject: Re: [PATCH stable 4.19 0/3] MMC timeout back ports
Date: Sat, 21 May 2022 16:40:44 +0200 [thread overview]
Message-ID: <Yoj57NDDiQblR5aT@kroah.com> (raw)
In-Reply-To: <1892af53-5d83-ac8a-1180-970bf07e8889@gmail.com>
On Thu, May 19, 2022 at 12:04:59PM -0700, Florian Fainelli wrote:
>
>
> On 5/19/2022 10:38 AM, Florian Fainelli wrote:
> >
> >
> > On 5/17/2022 11:22 AM, Florian Fainelli wrote:
> > > These 3 commits from upstream allow us to have more fine grained control
> > > over the MMC command timeouts and this solves the following timeouts
> > > that we have seen on our systems across suspend/resume cycles:
> > >
> > > [ 14.907496] usb usb2: root hub lost power or was reset
> > > [ 15.216232] usb 1-1: reset high-speed USB device number 2 using
> > > xhci-hcd
> > > [ 15.485812] bcmgenet 8f00000.ethernet eth0: Link is Down
> > > [ 15.525328] mmc1: error -110 doing runtime resume
> > > [ 15.531864] OOM killer enabled.
> > >
> > > Thanks!
> >
> > Looks like I managed to introduce a build warning due to the unused
> > timeout variable, let me submit a fresher version for 4.19, 4.14 and
> > 4.9.
>
> Only v4.19 and v4.14 required a v2, you can find both here:
>
> https://lore.kernel.org/lkml/20220519184536.370540-1-f.fainelli@gmail.com/T/#t
>
> https://lore.kernel.org/lkml/20220519190030.377695-1-f.fainelli@gmail.com/T/#t
>
> Sorry about that, I will build with W=1 in the future to notice those set
> but unused variable warnings.
I've queued up the updates now, thanks.
greg k-h
prev parent reply other threads:[~2022-05-21 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:22 [PATCH stable 4.19 0/3] MMC timeout back ports Florian Fainelli
2022-05-17 18:22 ` [PATCH stable 4.19 1/3] mmc: core: Specify timeouts for BKOPS and CACHE_FLUSH for eMMC Florian Fainelli
2022-05-17 18:22 ` [PATCH stable 4.19 2/3] mmc: block: Use generic_cmd6_time when modifying INAND_CMD38_ARG_EXT_CSD Florian Fainelli
2022-05-17 18:22 ` [PATCH stable 4.19 3/3] mmc: core: Default to generic_cmd6_time as timeout in __mmc_switch() Florian Fainelli
2022-05-19 17:38 ` [PATCH stable 4.19 0/3] MMC timeout back ports Florian Fainelli
2022-05-19 19:04 ` Florian Fainelli
2022-05-21 14:40 ` Greg Kroah-Hartman [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=Yoj57NDDiQblR5aT@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=CLoehle@hyperstone.com \
--cc=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=f.fainelli@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nishadkamdar@gmail.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).