public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.4 000/282] 5.4.243-rc1 review
Date: Wed, 17 May 2023 10:26:54 +0200	[thread overview]
Message-ID: <2023051744-overthrow-playlist-a0d5@gregkh> (raw)
In-Reply-To: <2023051738-bullfrog-dreamily-79a4@gregkh>

On Wed, May 17, 2023 at 10:25:13AM +0200, Greg Kroah-Hartman wrote:
> On Tue, May 16, 2023 at 08:52:13PM -0700, Guenter Roeck wrote:
> > On Mon, May 15, 2023 at 06:26:18PM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.4.243 release.
> > > There are 282 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, 17 May 2023 16:16:37 +0000.
> > > Anything received after that time might be too late.
> > > 
> > 
> > Build results:
> > 	total: 159 pass: 159 fail: 0
> > Qemu test results:
> > 	total: 455 pass: 454 fail: 1
> > Failed tests:
> > 	arm:sabrelite:multi_v7_defconfig:mtd2:mem256:net,default:imx6dl-sabrelite:rootfs
> > 
> > As far as I can see, the second SPI interface fails to instantiate.
> > 
> > [   21.491528] spi_imx 2008000.spi: bitbang start failed with -22
> > 
> > There are also various new warnings in clock code.
> > 
> > [   21.492631] WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:986 clk_core_disable+0x124/0x2e4
> > [   21.497524] WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:845 clk_core_unprepare+0x268/0x388
> > 
> > The warnings in clock code are gone after reverting all changes introducing
> > PM support for imx spi code. The boot failure is gone after reverting the
> > gpio conversion. In total, I reverted the following patches to fix the
> > boot and warning problems.
> > 
> > d6fcaa127cc6 Revert "spi: imx/fsl-lpspi: Convert to GPIO descriptors"
> > 9783b21b591d Revert "spi: imx: enable runtime pm support"
> > 4a8bdbf7462b Revert "spi: spi-imx: using pm_runtime_resume_and_get instead of pm_runtime_get_sync"
> > e6c5f497ff35 Revert "spi: imx: Don't skip cleanup in remove's error path"
> > d6ea758df74f Revert "spi: imx: fix runtime pm support for !CONFIG_PM"
> > b9dbd028c970 Revert "spi: imx: fix reference leak in two imx operations"
> > 
> > Is this really 5.4 material ?
> 
> You are right, this isn't 5.4 material (and really not 5.10 either for
> some of these changes.)  I'll go drop them all from 5.4.y and 5.10.y and
> push out -rc2 releases soon.

I'll leave the 5.10.y changes, they were sane.

thanks,

greg k-h

  reply	other threads:[~2023-05-17  8:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 16:26 [PATCH 5.4 000/282] 5.4.243-rc1 review Greg Kroah-Hartman
2023-05-15 16:30 ` [PATCH 5.4 227/282] rxrpc: Fix hard call timeout units Greg Kroah-Hartman
2023-05-15 20:09 ` [PATCH 5.4 000/282] 5.4.243-rc1 review Chris Paterson
2023-05-16  1:32 ` Shuah Khan
2023-05-16  9:12 ` Sudip Mukherjee (Codethink)
2023-05-16 11:20 ` Harshit Mogalapalli
2023-05-16 19:10 ` Naresh Kamboju
2023-05-17  3:52 ` Guenter Roeck
2023-05-17  8:25   ` Greg Kroah-Hartman
2023-05-17  8:26     ` Greg Kroah-Hartman [this message]
2023-05-17  8:58       ` Greg Kroah-Hartman
2023-05-17  7:55 ` Jon Hunter

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=2023051744-overthrow-playlist-a0d5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --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 \
    /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