Message ID | 20220713025657.3524506-1-yangyingliang@huawei.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: microchip-core: fix and cleanups | expand |
On 13/07/2022 03:56, Yang Yingliang wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Patch #1 fix a UAF in mchp_corespi_remove(). > Patch #2 and #3 some cleanups to simpify code. P sure I already gave you an R-b for patch 1, but for the series: Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > v1 -> v2: > add patch #3 to use dev_err_probe to simpify code. > > Yang Yingliang (3): > spi: microchip-core: fix UAF in mchp_corespi_remove() > spi: microchip-core: switch to use devm_spi_alloc_master() > spi: microchip-core: switch to use dev_err_probe() > > drivers/spi/spi-microchip-core.c | 56 ++++++++++++-------------------- > 1 file changed, 20 insertions(+), 36 deletions(-) > > -- > 2.25.1 >
On Wed, 13 Jul 2022 10:56:54 +0800, Yang Yingliang wrote: > Patch #1 fix a UAF in mchp_corespi_remove(). > Patch #2 and #3 some cleanups to simpify code. > > v1 -> v2: > add patch #3 to use dev_err_probe to simpify code. > > Yang Yingliang (3): > spi: microchip-core: fix UAF in mchp_corespi_remove() > spi: microchip-core: switch to use devm_spi_alloc_master() > spi: microchip-core: switch to use dev_err_probe() > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/3] spi: microchip-core: fix UAF in mchp_corespi_remove() commit: e82c6d62a1f2347cde69c169fcf37e4d26f89b98 [2/3] spi: microchip-core: switch to use devm_spi_alloc_master() commit: 5d56d8974d1e5fa5d7d0761037377e03f6edcc66 [3/3] spi: microchip-core: switch to use dev_err_probe() commit: cdeaf3a99a02b6f8566bcaacc9c3501c6cceda74 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