linux-kernel - Re: [PATCH] regulator: fan53880: Fix vsel_mask setting for FAN53880

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: <162316831090.28178.17660540178797301819.b4-ty@kernel.org>
Date:   Tue,  8 Jun 2021 17:06:32 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org,
        Christoph Fritz <chf.fritz@...glemail.com>
Subject: Re: [PATCH] regulator: fan53880: Fix vsel_mask setting for FAN53880_BUCK

On Mon, 7 Jun 2021 22:29:07 +0800, Axel Lin wrote:
> According to the datasheet:
> REGISTER DETAILS − 0x02 BUCK, BUCK_OUT is BIT0 ~ BIT7.
> 
> So vsel_mask for FAN53880_BUCK should be 0xFF.

Applied to

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

Thanks!

[1/1] regulator: fan53880: Fix vsel_mask setting for FAN53880_BUCK
      commit: 2e11737a772b95c6587df73f216eec1762431432

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