From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH 6/7] ASoC: ux500: Add missing module description
Date: Wed, 8 May 2024 11:19:05 +0200 [thread overview]
Message-ID: <20240508091909.27062-7-tiwai@suse.de> (raw)
In-Reply-To: <20240508091909.27062-1-tiwai@suse.de>
Now that make W=1 starts complaining the lack of MODULE_DESCRIPTION(),
let's add the missing information.
Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://lore.kernel.org/r/ZjpQm-hxLQtpgkUx@smile.fi.intel.com
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/soc/ux500/ux500_msp_dai.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/ux500/ux500_msp_dai.c b/sound/soc/ux500/ux500_msp_dai.c
index cde0dd8e2569..3fd13e8dd110 100644
--- a/sound/soc/ux500/ux500_msp_dai.c
+++ b/sound/soc/ux500/ux500_msp_dai.c
@@ -820,4 +820,5 @@ static struct platform_driver msp_i2s_driver = {
};
module_platform_driver(msp_i2s_driver);
+MODULE_DESCRIPTION("ASoC Ux500 I2S driver");
MODULE_LICENSE("GPL v2");
--
2.43.0
next prev parent reply other threads:[~2024-05-08 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 9:18 [PATCH 0/7] ASoC: Add missing module descriptions Takashi Iwai
2024-05-08 9:19 ` [PATCH 1/7] ASoC: ab8500: Add missing module description Takashi Iwai
2024-05-08 9:36 ` Andy Shevchenko
2024-05-08 9:19 ` [PATCH 2/7] ASoC: sigmadsp: " Takashi Iwai
2024-05-08 9:19 ` [PATCH 3/7] ASoC: qcom: Add missing module descriptions Takashi Iwai
2024-05-08 9:19 ` [PATCH 4/7] ASoC: dmaengine: Add missing module description Takashi Iwai
2024-05-08 9:19 ` [PATCH 5/7] ASoC: topology-test: " Takashi Iwai
2024-05-08 9:19 ` Takashi Iwai [this message]
2024-05-08 9:19 ` [PATCH 7/7] ASoC: xilinx: Add missing module descriptions Takashi Iwai
2024-05-08 9:22 ` [PATCH 0/7] ASoC: " Dragan Simic
2024-05-09 15:38 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240508091909.27062-7-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox