linux-kernel - Re: [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from device

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: <169262763557.266290.2836572378120379457.b4-ty@kernel.org>
Date:   Mon, 21 Aug 2023 15:20:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, lee@...nel.org, werneazc@...il.com
Cc:     linux-kernel@...r.kernel.org,
        Andre Werner <andre.werner@...tec-electronic.com>
Subject: Re: [PATCH v2 1/2] mfd: (tps65086): Read DEVICE ID register 1 from
 device

On Fri, 18 Aug 2023 10:37:21 +0200, werneazc@...il.com wrote:
> This commit prepares a following commit for the regulator part of the MFD.
> The driver should support different device chips that differ in their
> register definitions, for instance to control LDOA1 and SWB2.
> So it is necessary to use a dedicated regulator description for a
> specific device variant. Thus, the content from DEVICEID Register 1 is
> used to choose a dedicated configuration between the different device
> variants.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] mfd: (tps65086): Read DEVICE ID register 1 from device
      (no commit info)
[2/2] regulator: (tps65086): Select dedicated regulator config for chip variant
      commit: 3a5e6e49855661ad39b8fbb1dbd041178af98e00

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