[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <172774028424.2264837.4595727034314147956.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 00:51:24 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-rockchip@...ts.infradead.org,
Dragan Simic <dsimic@...jaro.org>
Cc: heiko@...ech.de, oss@...ene.moe, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH 0/5] Improve error handling in Rockchip SPI
drivers
On Thu, 26 Sep 2024 10:38:11 +0200, Dragan Simic wrote:
> This is a small series that improves error handling in the probe path
> of the Rockchip SPI drivers, by using dev_err_probe() properly in multiple
> places. It also removes one unnecessary check of a function return value,
> and performs a bunch of small, rather trivial code cleanups, to make the
> code neater and a bit easier to read.
>
> Dragan Simic (5):
> spi: rockchip: Perform trivial code cleanups
> spi: rockchip-sfc: Perform trivial code cleanups
> spi: rockchip: Don't check for failed get_fifo_len()
> spi: rockchip: Use dev_err_probe() in the probe path
> spi: rockchip-sfc: Use dev_err_probe() in the probe path
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/5] spi: rockchip: Perform trivial code cleanups
commit: d87ec94e48dd2da27fbe948f2dc6c8fedc98fff4
[2/5] spi: rockchip-sfc: Perform trivial code cleanups
commit: 6c510eac1528d8939bad8b6df72c7b23ffec8c25
[5/5] spi: rockchip-sfc: Use dev_err_probe() in the probe path
commit: 1482c40b440fa58f956bc3e1ef3426e0cdbc09e0
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
Powered by blists - more mailing lists