linux-kernel - Re: [PATCH] regulator: sy8824x: Fix ID table driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175140813407.710029.17246554557237585813.b4-ty@kernel.org>
Date: Tue, 01 Jul 2025 23:15:34 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jisheng Zhang <jszhang@...nel.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: sy8824x: Fix ID table driver_data

On Sun, 29 Jun 2025 17:59:05 +0800, Jisheng Zhang wrote:
> 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.
> 
> 

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