linux-kernel - Re: [PATCH] ASoC: dt-bindings: everest,es8326: Document interrupt 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: <173083052542.94172.3226642386925576095.b4-ty@kernel.org>
Date: Tue, 05 Nov 2024 18:15:25 +0000
From: Mark Brown <broonie@...nel.org>
To: Fei Shao <fshao@...omium.org>
Cc: Conor Dooley <conor+dt@...nel.org>, 
 David Yang <yangxiaohua@...rest-semi.com>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Rob Herring <robh@...nel.org>, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: everest,es8326: Document interrupt
 property

On Tue, 05 Nov 2024 17:18:11 +0800, Fei Shao wrote:
> The ES8326 audio codec has one interrupt pin for headset detection
> according to the datasheet. Document that in the binding.
> 
> This fixes dtbs_check error:
>   'interrupts-extended' does not match any of the regexes:
>   'pinctrl-[0-9]+'
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: dt-bindings: everest,es8326: Document interrupt property
      commit: 99348781d249817c8f96a7cbf636b7c6d74bd756

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