Messages in this thread | | | From | Mark Brown <> | Subject | Re: [PATCH] regmap: Handle sparse caches in the default sync | Date | Mon, 27 Mar 2023 14:22:57 +0100 |
| |
On Sat, 25 Mar 2023 21:49:49 +0000, Mark Brown wrote: > If there is no cache entry available we will get -ENOENT from the cache > implementation, handle this gracefully and skip rather than treating it as > an error. > >
Applied to
broonie/regmap.git for-next
Thanks!
[1/1] regmap: Handle sparse caches in the default sync commit: 2c89db8f8d1e544fd817d4c0dc508a00b78a8f7f
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
| |