linux-kernel - Re: [PATCH] ASoC: cs42l42: Report initial jack state

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: <163762561074.2471742.11078502974656470664.b4-ty@kernel.org>
Date:   Tue, 23 Nov 2021 00:00:10 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     patches@...nsource.cirrus.com, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org
Subject: Re: [PATCH] ASoC: cs42l42: Report initial jack state

On Fri, 19 Nov 2021 12:48:54 +0000, Richard Fitzgerald wrote:
> When a jack handler is registered in cs42l42_set_jack() the
> initial state should be reported if an attached headphone/headset
> has already been detected.
> 
> The jack detect sequence takes around 1 second: typically long
> enough for the machine driver to probe and register the jack handler
> in time to receive the first report from the interrupt handler. So
> it is possible on some systems that the correct initial state was seen
> simply because of lucky timing. Modular builds were more likely to
> miss the reporting of the initial state.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Report initial jack state
      commit: fdd535283779ec9f9c35fda352585c629121214f

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