linux-kernel - Re: [PATCH] ASoC: stm32: i2s: remove irqf

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: <166810706385.995851.10605818222907923454.b4-ty@kernel.org>
Date:   Thu, 10 Nov 2022 19:04:23 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Olivier Moysan <olivier.moysan@...s.st.com>,
        Takashi Iwai <tiwai@...e.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>
Cc:     linux-arm-kernel@...ts.infradead.org,
        linux-stm32@...md-mailman.stormreply.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: stm32: i2s: remove irqf_oneshot flag

On Thu, 10 Nov 2022 09:44:06 +0100, Olivier Moysan wrote:
> The IRQF_ONESHOT flag allows to ensure that the interrupt is not
> unmasked after the hard interrupt context handler has been executed
> and the thread has been woken. The interrupt line is unmasked after
> the thread handler function has been executed.
> 
> The STM32 I2S driver does not implement a threaded IRQ handler.
> So, the IRQF_ONESHOT flag is not useful in I2S driver.
> Remove this flag to allow the interrupt routine to be managed
> as a thread in RT mode.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: stm32: i2s: remove irqf_oneshot flag
      commit: 7c0f8f1462c9edeaa202a2cbea1bde0960434b09

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