linux-kernel - Re: [PATCH] ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect

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: <169022881228.1309709.2767178684192633298.b4-ty@kernel.org>
Date:   Mon, 24 Jul 2023 21:00:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com,
        Edson Juliano Drosdeck <edson.drosdeck@...il.com>
Cc:     perex@...ex.cz, tiwai@...e.com, wtli@...oton.com,
        u.kleine-koenig@...gutronix.de, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: nau8821: Add DMI quirk mechanism for active-high
 jack-detect

On Wed, 19 Jul 2023 17:02:41 -0300, Edson Juliano Drosdeck wrote:
> Add a quirk mechanism to allow specifying that active-high jack-detection
> should be used on platforms where this info is not available in devicetree.
> 
> And add an entry for the Positivo CW14Q01P-V2 to the DMI table, so that
> jack-detection will work properly on this laptop.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
      commit: 1bc40efdaf4a0ccfdb10a1c8e4b458f4764e8e5f

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