From: Pavel Machek <pavel@denx.de>
To: Pavel Machek <pavel@denx.de>
Cc: wsa+renesas@sang-engineering.com,
niklas.soderlund+renesas@ragnatech.se,
yoshihiro.shimoda.uh@renesas.com, geert+renesas@glider.be,
biju.das.jz@bp.renesas.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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 13:18:19 +0200 [thread overview]
Message-ID: <ZSUy+zA0+Chm6dFb@duo.ucw.cz> (raw)
In-Reply-To: <ZSRe78MAQwbBdyFP@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
Hi!
> > > This is the start of the stable review cycle for the 5.10.198 release.
> > > There are 226 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Wed, 11 Oct 2023 13:00:55 +0000.
> > > Anything received after that time might be too late.
> >
> > 4.14, 4.19 and 6.1 tests ok, 5.10 seems to have problems:
>
> Guessing from stack traces, these may be relevant:
So bisection reveals these are relevant:
|e10d3d256 b161d8 o: 5.10| mmc: renesas_sdhi: probe into TMIO after SCC parameters have been setup
Ok
|493b70c48 d14ac6 o: 5.10| mmc: renesas_sdhi: populate SCC pointer at the proper place
Testing now: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1031822035
|c508545f4 0d856c o: 5.10| mmc: tmio: support custom irq masks
|8df1f0639 74f45d o: 5.10| mmc: renesas_sdhi: register irqs before registering controller
Fail: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1031786077
I should be able to point specific commit with two more tests.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-10-10 11:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:59 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 [this message]
2023-10-10 12:05 ` Pavel Machek
2023-10-10 19:07 ` Wolfram Sang
2023-10-10 19:14 ` Greg Kroah-Hartman
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=ZSUy+zA0+Chm6dFb@duo.ucw.cz \
--to=pavel@denx.de \
--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=gregkh@linuxfoundation.org \
--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=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
all inboxes | Powered by JetHome®