[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172471182196.865478.11843966952043605315.b4-ty@kernel.org>
Date: Mon, 26 Aug 2024 23:37:01 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
alsa-devel@...a-project.org, Liao Chen <liaochen4@...wei.com>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
cezary.rojewski@...el.com, pierre-louis.bossart@...ux.intel.com,
peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com,
u.kleine-koenig@...gutronix.de, andy.shevchenko@...il.com,
kuninori.morimoto.gx@...esas.com, robh@...nel.org
Subject: Re: [PATCH -next 0/4] ASoC: fix module autoloading
On Mon, 26 Aug 2024 08:49:20 +0000, Liao Chen wrote:
> This patchset aims to enable autoloading of some use modules.
> By registering MDT, the kernel is allowed to automatically bind
> modules to devices that match the specified compatible strings.
>
> Liao Chen (4):
> ASoC: intel: fix module autoloading
> ASoC: google: fix module autoloading
> ASoC: tda7419: fix module autoloading
> ASoC: fix module autoloading
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/4] ASoC: intel: fix module autoloading
commit: ae61a3391088d29aa8605c9f2db84295ab993a49
[2/4] ASoC: google: fix module autoloading
commit: 8e1bb4a41aa78d6105e59186af3dcd545fc66e70
[3/4] ASoC: tda7419: fix module autoloading
commit: 934b44589da9aa300201a00fe139c5c54f421563
[4/4] ASoC: fix module autoloading
commit: 1165e70a4a5d8b4da77002ac22b4c5397f30e00d
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