Message ID | cover.1598594714.git.viresh.kumar@linaro.org (mailing list archive) |
---|---|
Headers | show |
Series | opp: Unconditionally call dev_pm_opp_of_remove_table() | expand |
On 28-08-20, 11:37, Viresh Kumar wrote: > Hello, > > This cleans up some of the user code around calls to > dev_pm_opp_of_remove_table(). > > All the patches can be picked by respective maintainers directly except > for the last patch, which needs the previous two to get merged first. > > These are based for 5.9-rc1. > Viresh Kumar (8): > cpufreq: imx6q: Unconditionally call dev_pm_opp_of_remove_table() > drm/lima: Unconditionally call dev_pm_opp_of_remove_table() > drm/msm: Unconditionally call dev_pm_opp_of_remove_table() > mmc: sdhci-msm: Unconditionally call dev_pm_opp_of_remove_table() > spi: spi-geni-qcom: Unconditionally call dev_pm_opp_of_remove_table() > spi: spi-qcom-qspi: Unconditionally call dev_pm_opp_of_remove_table() > tty: serial: qcom_geni_serial: Unconditionally call > dev_pm_opp_of_remove_table() > qcom-geni-se: remove has_opp_table During testing by some of the Linaro folks on linux-next, we found out that there was a bug in the OPP core (which makes the kernel crash in some corner cases with these patches) for which I have sent a fix today which should be part of 5.9-rc4: https://lore.kernel.org/lkml/922ff0759a16299e24cacfc981ac07914d8f1826.1598865786.git.viresh.kumar@linaro.org/ Please apply the patches over rc4 only once it comes out (I will confirm by that time once the patch gets merged). Else you guys can provide your Ack and I can take the patches through OPP tree.
On 31-08-20, 16:39, Viresh Kumar wrote: > On 28-08-20, 11:37, Viresh Kumar wrote: > > Hello, > > > > This cleans up some of the user code around calls to > > dev_pm_opp_of_remove_table(). > > > > All the patches can be picked by respective maintainers directly except > > for the last patch, which needs the previous two to get merged first. > > > > These are based for 5.9-rc1. > > > Viresh Kumar (8): > > cpufreq: imx6q: Unconditionally call dev_pm_opp_of_remove_table() > > drm/lima: Unconditionally call dev_pm_opp_of_remove_table() > > drm/msm: Unconditionally call dev_pm_opp_of_remove_table() > > mmc: sdhci-msm: Unconditionally call dev_pm_opp_of_remove_table() > > spi: spi-geni-qcom: Unconditionally call dev_pm_opp_of_remove_table() > > spi: spi-qcom-qspi: Unconditionally call dev_pm_opp_of_remove_table() > > tty: serial: qcom_geni_serial: Unconditionally call > > dev_pm_opp_of_remove_table() > > qcom-geni-se: remove has_opp_table > > During testing by some of the Linaro folks on linux-next, we found out > that there was a bug in the OPP core (which makes the kernel crash in > some corner cases with these patches) for which I have sent a fix > today which should be part of 5.9-rc4: > > https://lore.kernel.org/lkml/922ff0759a16299e24cacfc981ac07914d8f1826.1598865786.git.viresh.kumar@linaro.org/ > > Please apply the patches over rc4 only once it comes out (I will > confirm by that time once the patch gets merged). Else you guys can > provide your Ack and I can take the patches through OPP tree. The fix got merged in 5.9-rc4, please apply the patches from this series in your trees and base them on rc4. Thanks.
On Fri, 28 Aug 2020 11:37:45 +0530, Viresh Kumar wrote: > This cleans up some of the user code around calls to > dev_pm_opp_of_remove_table(). > > All the patches can be picked by respective maintainers directly except > for the last patch, which needs the previous two to get merged first. > > These are based for 5.9-rc1. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/2] spi: spi-geni-qcom: Unconditionally call dev_pm_opp_of_remove_table() commit: 7d568edff5cb7968cc5f29e85da15f941b8070b8 [2/2] spi: spi-qcom-qspi: Unconditionally call dev_pm_opp_of_remove_table() commit: 062cf7fc927d2546b58ed128383e5c52f26a00a5 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