From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Pavel Machek <pavel@denx.de>,
niklas.soderlund+renesas@ragnatech.se,
yoshihiro.shimoda.uh@renesas.com, geert+renesas@glider.be,
biju.das.jz@bp.renesas.com, Chris.Paterson2@renesas.com,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org
Subject: Re: renesas_sdhi problems in 5.10-stable was Re: [PATCH 5.10 000/226] 5.10.198-rc1 review
Date: Tue, 10 Oct 2023 21:14:48 +0200 [thread overview]
Message-ID: <2023101057-runny-pellet-8952@gregkh> (raw)
In-Reply-To: <ZSWg1fv3gOyV5t+h@shikoro>
On Tue, Oct 10, 2023 at 09:07:01PM +0200, Wolfram Sang wrote:
> Hi Pavel,
>
> > And testing failed. So
> >
> > commit f5799b4e142884c2e7aa99f813113af4a3395ffb
> > Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > Date: Tue Nov 10 15:20:57 2020 +0100
> >
> > mmc: renesas_sdhi: populate SCC pointer at the proper place
> >
> > [ Upstream commit d14ac691bb6f6ebaa7eeec21ca04dd47300ff5b6 ]
> >
> > seems to be the buggy commit that breaks renesas boards in 5.10.
>
> This patch was part of a series. Did the other two patches come with it?
>
> b161d87dfd3d ("mmc: renesas_sdhi: probe into TMIO after SCC parameters have been setup")
Yes.
> 45bffc371fef ("mmc: renesas_sdhi: only reset SCC when its pointer is populated")
No :(
> If not, I could imagine that could lead to a crash. No idea why only
> with 5.10, though.
The above commit is only in 5.11, so newer kernels should be fine.
I'll go queue up the one missing patch now, thanks.
greg k-h
next prev parent reply other threads:[~2023-10-10 19:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:59 [PATCH 5.10 000/226] 5.10.198-rc1 review Greg Kroah-Hartman
2023-10-09 19:33 ` Pavel Machek
2023-10-09 20:13 ` renesas_sdhi problems in 5.10-stable was " Pavel Machek
2023-10-10 11:18 ` Pavel Machek
2023-10-10 12:05 ` Pavel Machek
2023-10-10 19:07 ` Wolfram Sang
2023-10-10 19:14 ` Greg Kroah-Hartman [this message]
2023-10-24 19:22 ` Pavel Machek
2023-10-25 10:47 ` Geert Uytterhoeven
2023-10-25 10:53 ` Geert Uytterhoeven
2023-10-25 12:35 ` Geert Uytterhoeven
2023-10-25 17:05 ` Geert Uytterhoeven
2023-10-25 18:39 ` Guenter Roeck
2023-10-25 19:53 ` Geert Uytterhoeven
2023-10-25 21:26 ` Geert Uytterhoeven
2023-10-26 12:08 ` Geert Uytterhoeven
2023-10-26 12:20 ` Geert Uytterhoeven
2023-10-25 22:00 ` Pavel Machek
2023-10-26 1:23 ` Guenter Roeck
2023-10-09 20:24 ` Florian Fainelli
2023-10-09 22:57 ` Shuah Khan
2023-10-10 9:57 ` Jon Hunter
2023-10-10 18:18 ` Guenter Roeck
2023-10-11 1:40 ` Naresh Kamboju
2023-10-11 6:47 ` luomeng
2023-10-11 9:18 ` Pavel Machek
2023-10-11 9:38 ` Pavel Machek
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=2023101057-runny-pellet-8952@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Paterson2@renesas.com \
--cc=akpm@linux-foundation.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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