linux-kernel - Re: [PATCH 0/3] ASoC: da7219: Add jack insertion detection polarity

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]

Date:   Wed, 24 May 2023 12:04:29 +0100
From:   Mark Brown <broonie@...nel.org>
To:     conor+dt@...nel.org,
        David Rau <David.Rau.opensource@...renesas.com>
Cc:     support.opensource@...semi.com, lgirdwood@...il.com,
        robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        perex@...ex.cz, tiwai@...e.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/3] ASoC: da7219: Add jack insertion detection
 polarity

On Tue, 23 May 2023 16:18:18 +0000, David Rau wrote:
> This patchset adds the support of DA7219 Jack insertion detection
> polarity selection.
> 
> The first patch replaces the old txt binding with a new schema binding.
> 
> The second patch adds `dlg,jack-ins-det-pty` property for Jack
> insertion detection polarity selection.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: dt-bindings: dialog,da7219: convert to dtschema
      commit: 345585b776e6f6f1cab846eb3efbef32c53fc0e3
[2/3] ASoC: dt-bindings: da7219: Add jack-ins-det-pty property
      commit: c28dc3bdfcd9e93b6cf1f3f0bb3c51e819fc977f
[3/3] ASoC: da7219: Add Jack insertion detection polarity
      commit: dc0ff0fa3a9bf9f7be3a9530f8f6079324f54fa5

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