linux-kernel - Re: [PATCH v1] ASoC: cs42l42: Fallback to headphones for type 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: <166429012122.444806.6143435073545852825.b4-ty@kernel.org>
Date:   Tue, 27 Sep 2022 15:48:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Stefan Binding <sbinding@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH v1] ASoC: cs42l42: Fallback to headphones for type detect

On Tue, 27 Sep 2022 13:14:40 +0100, Stefan Binding wrote:
> After tip sense detects a jack insertion, if automatic
> type detection, and manual type detection fails, then
> fall back to assume the jack connected belongs to
> headphones.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Fallback to headphones for type detect
      commit: 45560891506fae31be66f2a73693c5c8bd7dbedb

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