linux-kernel - Re: [PATCH] regulator: rt6160: Remove vsel_active_low from struct rt6160

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1623770667.4571.4.camel@richtek.com>
Date:   Tue, 15 Jun 2021 15:24:27 +0000
From:   cy_huang(黃啟原) <cy_huang@...htek.com>
To:     "broonie@...nel.org" <broonie@...nel.org>,
        "axel.lin@...ics.com" <axel.lin@...ics.com>
CC:     "lgirdwood@...il.com" <lgirdwood@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: rt6160: Remove vsel_active_low from struct
 rt6160_priv

Hi, Mark/Axel:
No, you may misunderstand it.
If vsel active is high, the normal voltage output register is vselh register,
and the suspend voltage is vsell register. Else, reverse.

Axel's change will cause the normal/suspend voltage be configured for the same
register. It's not for our reference usage.
> On Tue, 15 Jun 2021 18:39:47 +0800, Axel Lin wrote:
> >
> > Use a local variable instead is enough, this simplifies the code.
> Applied to
>
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-
> next
>
> Thanks!
>
> [1/1] regulator: rt6160: Remove vsel_active_low from struct rt6160_priv
>       commit: f3f4f37d53be578c65dd32a1ffad432b33aef236
>
> 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
************* Email Confidentiality Notice ********************

The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!