linux-kernel - Re: [PATCH 1/2] ASoC: amd: ps: update license

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: <170863621521.109182.12917169383809652232.b4-ty@kernel.org>
Date: Thu, 22 Feb 2024 21:10:15 +0000
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, Mario.Limonciello@....com, 
 venkataprasad.potturu@....com, Basavaraj.Hiregoudar@....com, 
 Sunil-kumar.Dommati@....com, syed.sabakareem@....com, lgirdwood@...il.com, 
 perex@...ex.cz, tiwai@...e.com, linux-kernel@...r.kernel.org, 
 linux-sound@...r.kernel.org, arnd@...db.de
Subject: Re: [PATCH 1/2] ASoC: amd: ps: update license

On Thu, 22 Feb 2024 15:56:55 +0530, Vijendar Mukunda wrote:
> To align with AMD SoundWire manager driver license, update license as
> GPL-2.0-only for Pink Sardine ACP PCI driver and corresponding child
> drivers.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: amd: ps: update license
      commit: 4c75493833a6e2095f03639f66aed5fbf2683c73
[2/2] ASoC: amd: ps: modify ACP register end address macro
      commit: 253ce07d2a091e98ef53e700e7fa221b28c4f964

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