linux-kernel - Re: [PATCH -next] regulator: max77857: fix build error in max77857-regulator.c

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: <169108279253.101361.17554873393558395381.b4-ty@kernel.org>
Date:   Thu, 03 Aug 2023 18:13:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Yang Yingliang <yangyingliang@...wei.com>
Cc:     lgirdwood@...il.com, okan.sahin@...log.com
Subject: Re: [PATCH -next] regulator: max77857: fix build error in
 max77857-regulator.c

On Thu, 03 Aug 2023 19:36:54 +0800, Yang Yingliang wrote:
> When using low verion gcc(7.5) to build the max77857-regulator driver,
> got the following error:
> 
> drivers/regulator/max77857-regulator.c:312:16: error: initializer element is not constant
>   .ramp_delay = max77857_ramp_table[0][0],
> 
> To fix this by introducing a macro RAMAP_DELAY_INIT_VAL to define the
> value of max77857_ramp_table[0[0].
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: max77857: fix build error in max77857-regulator.c
      commit: 93083725e1ed86c07ea9846bb573b9340985853f

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