From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Marek Vasut <marex@denx.de>,
Linux Stable <stable@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Dinghao Liu <dinghao.liu@zju.edu.cn>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: Possibly broken Linux 5.10.198 backport spi: spi-zynqmp-gqspi: Fix runtime PM imbalance in zynqmp_qspi_probe
Date: Sun, 15 Oct 2023 12:29:37 +0700 [thread overview]
Message-ID: <ZSt4wfx1EMeC0lnX@debian.me> (raw)
In-Reply-To: <ZSrERw6ucvl1wLWX@sashalap>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Sat, Oct 14, 2023 at 12:39:35PM -0400, Sasha Levin wrote:
> On Fri, Oct 13, 2023 at 12:39:23PM +0700, Bagas Sanjaya wrote:
> > On Thu, Oct 12, 2023 at 06:39:10PM +0200, Marek Vasut wrote:
> > > Linux 5.10.198 commit
> > > 2cdec9c13f81 ("spi: spi-zynqmp-gqspi: Fix runtime PM imbalance in
> > > zynqmp_qspi_probe")
> > >
> > > looks very different compared to matching upstream commit:
> > > a21fbc42807b ("spi: spi-zynqmp-gqspi: Fix runtime PM imbalance in
> > > zynqmp_qspi_probe")
> > >
> > > The Linux 5.10.198 change breaks a platform for me and it really looks like
> > > an incorrect backport.
> > >
> > > Dinghao, can you have a look ?
> > >
> >
> > Thanks for the regression report. I'm adding it to regzbot (as stable-specific
> > one):
> >
> > #regzbot ^introduced: 2cdec9c13f81
>
> I'm going to revert it from 5.10.
>
OK, thanks!
Don't forget to add Link: to this regression report and most importantly,
Fixes: to the culprit commit when reverting.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-15 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 16:39 Possibly broken Linux 5.10.198 backport spi: spi-zynqmp-gqspi: Fix runtime PM imbalance in zynqmp_qspi_probe Marek Vasut
2023-10-13 5:39 ` Bagas Sanjaya
2023-10-14 16:39 ` Sasha Levin
2023-10-15 5:29 ` Bagas Sanjaya [this message]
2023-11-02 8:40 ` Linux regression tracking #update (Thorsten Leemhuis)
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=ZSt4wfx1EMeC0lnX@debian.me \
--to=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=dinghao.liu@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=marex@denx.de \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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