regulator: sy8824x: Fix ID table driver_data
PATCH 1/1 regulator: sy8824x: Fix ID table driver_data
Currently, the driver_data of the i2c ID table is wrong, so it won't work if any sy8824x user makes use of the ID table. Fortunately, there's no such user in upstream source code, we can fix the issue by using different ID table entry for sy8824c, sy8824e, sy20276 and sy20278.
--- drivers/regulator/sy8824x.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/regulator/sy8824x.c +4 -1
@@ -213,7 +213,10 @@ static const struct of_device_id sy8824_dt_ids[] = {MODULE_DEVICE_TABLE (of, sy8824_dt_ids);static const struct i2c_device_id sy8824_id[] = { - {"sy8824" , (kernel_ulong_t)&sy8824c_cfg }, + {"sy8824c" , (kernel_ulong_t)&sy8824c_cfg }, + {"sy8824e" , (kernel_ulong_t)&sy8824e_cfg }, + {"sy20276" , (kernel_ulong_t)&sy20276_cfg }, + {"sy20278" , (kernel_ulong_t)&sy20278_cfg }, { } };MODULE_DEVICE_TABLE (i2c, sy8824_id);
Signature · 1 line
2.49.0
Mark Brown
maintainerQuoted 6 lines · Jisheng Zhang
Currently, the
driver_dataof the i2c ID table is wrong, so it won't work if any sy8824x user makes use of the ID table. Fortunately, there's no such user in upstream source code, we can fix the issue by using different ID table entry for sy8824c, sy8824e, sy20276 and sy20278.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: sy8824x: Fix ID table driver_data
commit: f172ffde18997aa401a74153cea4ae3bfdcb5124
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