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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6f9d7066-9592-4a14-a811-c2451cbc33fa@quicinc.com>
Date: Tue, 4 Jun 2024 17:02:06 -0700
From: Jeff Johnson <quic_jjohnson@...cinc.com>
To: Mark Brown <broonie@...nel.org>
CC: 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 6/4/2024 7:14 AM, Mark Brown wrote:
> On Tue, Jun 04, 2024 at 06:59:31AM -0700, Jeff Johnson wrote:
>> On 6/4/2024 4:56 AM, Mark Brown wrote:
> 
>>> 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.
> 
>> https://bugzilla.kernel.org/show_bug.cgi?id=10770
> 
> Please include human readable descriptions of things like commits and
> issues being discussed in e-mail in your mails, this makes them much
> easier for humans to read especially when they have no internet access.
> I do frequently catch up on my mail on flights or while otherwise
> travelling so this is even more pressing for me than just being about
> making things a bit easier to read.
> 
> and I'm not seeing anything in the above link that articulates an actual
> use case.

Sorry for the terse response. I agree with others that it was premature to
enable the warnings before all the instances were cleaned. But since things
are as they are, and since I saw others had 100% cleaned drivers/net, I took
it upon myself to clean up some other top-level directories without worrying
about if it made sense or not.

/jeff

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ