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: <172927342605.163659.12231131431088875442.b4-ty@kernel.org>
Date: Fri, 18 Oct 2024 18:43:46 +0100
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert+renesas@...der.be>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>, 
 Prabhakar <prabhakar.csengg@...il.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-renesas-soc@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>, 
 Fabrizio Castro <fabrizio.castro.jz@...esas.com>, 
 Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH] ASoC: rsnd: Refactor port handling with helper for
 endpoint node selection

On Fri, 11 Oct 2024 18:53:46 +0100, Prabhakar wrote:
> Refactor the code responsible for selecting the correct device node for
> audio endpoint parsing in the rsnd driver. A new helper function
> `rsnd_pick_endpoint_node_for_ports()` is introduced to handle the
> selection of the endpoint node by checking whether the port is named
> 'port' or 'ports'.
> 
> This change simplifies the logic in both `rsnd_dai_of_node()` and
> `rsnd_dai_probe()` functions by replacing repetitive condition checks
> with the new helper.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: rsnd: Refactor port handling with helper for endpoint node selection
      commit: daf5e3c68144bdb7e605f46853febc7bb257d44d

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ