linux-kernel - Re: [PATCH] ASoC: sh: rz-ssi: Fix error message print

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: <170663505112.44782.17133777488665631333.b4-ty@kernel.org>
Date: Tue, 30 Jan 2024 17:17:31 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Geert Uytterhoeven <geert+renesas@...der.be>, 
 Prabhakar <prabhakar.csengg@...il.com>
Cc: linux-sound@...r.kernel.org, linux-renesas-soc@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>, 
 Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH] ASoC: sh: rz-ssi: Fix error message print

On Tue, 30 Jan 2024 15:08:22 +0000, Prabhakar wrote:
> The devm_request_irq() call is done for "dma_rt" interrupt but the error
> message printed "dma_tx" interrupt on failure, fix this by updating
> dma_tx -> dma_rt in dev_err_probe() message. While at it aligned the code.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: sh: rz-ssi: Fix error message print
      commit: 9a6d7c4fb2801b675a9c31a7ceb78c84b8c439bc

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