linux-kernel - Re: [PATCH] ASoC: SOF: sof-of-dev: add parameter to override tplg/fw

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: <172927343394.163659.7634673510798036454.b4-ty@kernel.org>
Date: Fri, 18 Oct 2024 18:43:53 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, Daniel Baluta <daniel.baluta@....com>
Cc: lgirdwood@...il.com, ranjani.sridharan@...ux.intel.com, 
 kai.vehmanen@...ux.intel.com, linux-kernel@...r.kernel.org, 
 Anne Onciulescu <anne.onciulescu@...il.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Chao Song <chao.song@...ux.intel.com>, 
 Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>
Subject: Re: [PATCH] ASoC: SOF: sof-of-dev: add parameter to override
 tplg/fw_filename

On Thu, 17 Oct 2024 14:03:13 +0300, Daniel Baluta wrote:
> Add support to override topology and firmware filename,
> using module parameters. This is helpful for development
> and also for testing various scenarios.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: SOF: sof-of-dev: add parameter to override tplg/fw_filename
      commit: 9cb86a9cf12504c8dd60b40a6a200856852c1813

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