linux-kernel - Re: [PATCH v2 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172415785240.39606.6131661518510605412.b4-ty@kernel.org>
Date: Tue, 20 Aug 2024 13:44:12 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, vkoul@...nel.org, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>
Cc: vinod.koul@...aro.org, linux-kernel@...r.kernel.org, tiwai@...e.de, 
 pierre-louis.bossart@...ux.intel.com, bard.liao@...el.com
Subject: Re: [PATCH v2 0/3] ALSA/ASoC/SoundWire: Intel: update maximum
 number of links

On Mon, 19 Aug 2024 08:55:45 +0800, Bard Liao wrote:
> Intel new platforms can have up to 5 SoundWire links.
> This series does not apply to SoundWire tree due to recent changes in
> machine driver. Can we go via ASoC tree with Vinod's Acked-by tag?
> 
> v2:
>  - Change the patch order as per Vinod's suggestion
> 
> [...]

Applied to

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

Thanks!

[1/3] ALSA/ASoC/SoundWire: Intel: use single definition for SDW_INTEL_MAX_LINKS
      commit: b27404b2bbf951a11500525dea15681cc970226c
[2/3] soundwire: intel: add probe-time check on link id
      commit: d2234596be2192d9c1ae34f8c7534531191bc433
[3/3] soundwire: intel: increase maximum number of links
      commit: 1f3662838a05f1ab6af89a417f6f252d91d0806b

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