On Fri, 03 May 2024 09:03:50 -0500, Pierre-Louis Bossart wrote: > This patchset does not change any functionality. It only clarifies the > Copyright information in ASoC/HDAudio contributions, where an "All > rights reserved" notice was mistakenly added in a number of files over > the years, likely due to copy/paste. The Intel template never included > this statement. > > I chose to group all these patches together, they could be merged with > either of the ALSA or the ASoC tree. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/9] ASoC: SOF: Intel: clarify Copyright information commit: 293ad28116e2c3e4d3eb28bd0378558edc897f55 [2/9] ASoC: Intel: boards: clarify Copyright information commit: 0e0440535de8e7c5c0ae0bd469b6ae184f9c732c [3/9] ASoC: Intel: common: clarify Copyright information commit: 5cf4ffa4113da2e797c8281bac2838d29f5a03bf [4/9] ASoC: codecs: Intel: clarify Copyright information commit: 884077bd7110db61eddff086f9ab7f2c6748d169 [5/9] ASoC: Intel: catpt: clarify Copyright information commit: 618ae0d7e740d212044ba25d0f1013374eda448a [6/9] ASoC: Intel: avs: clarify Copyright information commit: 94001147a09ffeaf0657db7c189af77cda427f30 [7/9] ASoC: soc-topology-test: clarify Copyright information commit: 83e495d7b29b663861c68a1ad77710b6315472ad 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
