linux-kernel - Re: [PATCH] regulator: lp872x: Remove lp872x_dvs

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 for Android: free password hash cracker in your pocket

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

Message-Id: <163482376874.1547520.6448484830004949384.b4-ty@kernel.org>
Date:   Thu, 21 Oct 2021 14:42:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Nathan Chancellor <nathan@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, llvm@...ts.linux.dev,
        linux-kernel@...r.kernel.org,
        Maíra Canal <maira.canal@....br>,
        Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: [PATCH] regulator: lp872x: Remove lp872x_dvs_state

On Mon, 18 Oct 2021 17:43:35 -0700, Nathan Chancellor wrote:
> After this driver was converted to gpiod, clang started warning:
> 
> vers/regulator/lp872x.c:689:57: error: implicit conversion from
> enumeration type 'enum lp872x_dvs_state' to different enumeration type
> 'enum gpiod_flags' [-Werror,-Wenum-conversion]
>         dvs->gpio = devm_gpiod_get_optional(lp->dev, "ti,dvs", pinstate);
>                     ~~~~~~~~~~~~~~~~~~~~~~~                    ^~~~~~~~
> 1 error generated.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: lp872x: Remove lp872x_dvs_state
      commit: 061514dbfb79910ef60eb40dd9fc528be3f45d62

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