[PATCH] ASoC: qcom: lpass-sc7180: Add MODULE_DEVICE_TABLE

[PATCH] ASoC: qcom: lpass-sc7180: Add MODULE_DEVICE_TABLE

[Douglas Anderson]

The lpass-sc7180 driver can be built as a module but is lacking a
MODULE_DEVICE_TABLE.  This means it won't auto-load.  Fix this
oversight.

Fixes: 24caf8d9eb10 ("ASoC: qcom: lpass-sc7180: Add platform driver for lpass audio")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---

 sound/soc/qcom/lpass-sc7180.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sound/soc/qcom/lpass-sc7180.c b/sound/soc/qcom/lpass-sc7180.c
index 167bf2cbc556..a8a3d8f8f567 100644
--- a/sound/soc/qcom/lpass-sc7180.c
+++ b/sound/soc/qcom/lpass-sc7180.c
@@ -200,6 +200,7 @@ static const struct of_device_id sc7180_lpass_cpu_device_id[] = {
 	{.compatible = "qcom,sc7180-lpass-cpu", .data = &sc7180_data},
 	{}
 };
+MODULE_DEVICE_TABLE(of, sc7180_lpass_cpu_device_id);
 
 static struct platform_driver sc7180_lpass_cpu_platform_driver = {
 	.driver = {
-- 
2.28.0.618.gf4bc123cb7-goog

Re: [PATCH] ASoC: qcom: lpass-sc7180: Add MODULE_DEVICE_TABLE

[Mark Brown]

On Wed, 16 Sep 2020 11:15:55 -0700, Douglas Anderson wrote:
> The lpass-sc7180 driver can be built as a module but is lacking a
> MODULE_DEVICE_TABLE.  This means it won't auto-load.  Fix this
> oversight.

Applied to

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

Thanks!

[1/1] ASoC: qcom: lpass-sc7180: Add MODULE_DEVICE_TABLE
      commit: dcde34c47d8f7befc647fda65e8efa8cc0e795ca

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