linux-kernel - Re: [PATCH] ASoC: meson: meson-card-utils: use of_property

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: <174558344482.35587.18106901736438016481.b4-ty@kernel.org>
Date: Fri, 25 Apr 2025 13:17:24 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, linux-amlogic@...ts.infradead.org, 
 Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: jbrunet@...libre.com, lgirdwood@...il.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 Christian Hewitt <christianshewitt@...il.com>, stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: meson: meson-card-utils: use
 of_property_present() for DT parsing

On Sat, 19 Apr 2025 23:34:48 +0200, Martin Blumenstingl wrote:
> Commit c141ecc3cecd ("of: Warn when of_property_read_bool() is used on
> non-boolean properties") added a warning when trying to parse a property
> with a value (boolean properties are defined as: absent = false, present
> without any value = true). This causes a warning from meson-card-utils.
> 
> meson-card-utils needs to know about the existence of the
> "audio-routing" and/or "audio-widgets" properties in order to properly
> parse them. Switch to of_property_present() in order to silence the
> following warning messages during boot:
>   OF: /sound: Read of boolean property 'audio-routing' with a value.
>   OF: /sound: Read of boolean property 'audio-widgets' with a value.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: meson: meson-card-utils: use of_property_present() for DT parsing
      commit: 171eb6f71e9e3ba6a7410a1d93f3ac213f39dae2

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