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: <173083364104.105724.13341920313310122179.b4-ty@kernel.org>
Date: Tue, 05 Nov 2024 19:07:21 +0000
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, yung-chuan.liao@...ux.intel.com, 
 ranjani.sridharan@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com, 
 venkataprasad.potturu@....com, Mario.Limonciello@....com, 
 Richard.Gong@....com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Liam Girdwood <liam.r.girdwood@...el.com>
Subject: Re: [PATCH 0/2] Soundwire dai link init logic refactor

On Fri, 01 Nov 2024 07:38:00 +0530, Vijendar Mukunda wrote:
> This patch series refactors the SoundWire dai link init logic for Intel
> and AMD generic SoundWire machine driver and also updates the stream_name
> in dai_links structure.
> 
> Link: https://github.com/thesofproject/linux/pull/5218
> Reviewed-by: Bard Liao <yung-chuan.liao@...ux.intel.com>
> Reviewed-by: Liam Girdwood <liam.r.girdwood@...el.com>
> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: sdw_utils/intel/amd: refactor dai link init logic
      commit: 485df22866559e2f821a9754d51a9755ce56e7aa
[2/2] ASoC: sdw_utils: Update stream_name in dai_links structure
      commit: d280cf5fbfe3cdd373c98e858834ff87b6ea64de

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