[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <04bfcdd0088f521e4418a77e528652e3@manjaro.org>
Date: Tue, 04 Jun 2024 21:20:49 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Jeff Johnson <quic_jjohnson@...cinc.com>, Srinivas Kandagatla
<srinivas.kandagatla@...aro.org>, Banajit Goswami <bgoswami@...cinc.com>,
Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org, kernel@...cinc.com
Subject: Re: [PATCH] ASoC: qcom: add missing MODULE_DESCRIPTION() macro
On 2024-06-04 13:56, Mark Brown wrote:
> On Mon, Jun 03, 2024 at 05:16:07PM -0700, Jeff Johnson wrote:
>> make allmodconfig && make W=1 C=1 reports:
>> WARNING: modpost: missing MODULE_DESCRIPTION() in
>> sound/soc/qcom/snd-soc-qcom-sdw.o
>
> Is anyone getting any value from these MODULE_DESCRIPTION()s? This all
> just seems like a huge amount of noise and I'm having trouble thinking
> of a use case.
FWIW, I find module descriptions useful. Of course, there are
some of them that don't provide much value, but the well-written
ones are good.
Powered by blists - more mailing lists