linux-kernel - Re: [PATCH v1 0/2] spi: pxa2xx: Fix module reloading failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <172434346939.724581.4660359175947229932.b4-ty@kernel.org>
Date: Thu, 22 Aug 2024 17:17:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>, 
 linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Daniel Mack <daniel@...que.org>, 
 Haojian Zhuang <haojian.zhuang@...il.com>, 
 Robert Jarzmik <robert.jarzmik@...e.fr>
Subject: Re: [PATCH v1 0/2] spi: pxa2xx: Fix module reloading failure

On Thu, 22 Aug 2024 14:30:52 +0300, Andy Shevchenko wrote:
> After splitting platform and reworking PCI drivers the module
> reloading became broken as reported by Hao. Here is the patch
> to fix that along with another one that fixes PM runtime workflow
> differences between the busses (PCI vs. platform).
> 
> This is material for v6.11 as the initial work landed there and we still
> have time to fix it before the release.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] spi: pxa2xx: Do not override dev->platform_data on probe
      commit: 9a8fc292dd93b93db30e01c94c0da4c944852f28
[2/2] spi: pxa2xx: Move PM runtime handling to the glue drivers
      commit: e17465f78eb92ebb4be17e35d6c0584406f643a0

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark