mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Mark Brown <broonie@kernel.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Banajit Goswami <bgoswami@quicinc.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	<alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
	<kernel@quicinc.com>
Subject: Re: [PATCH] ASoC: qcom: add missing MODULE_DESCRIPTION() macro
Date: Tue, 4 Jun 2024 17:02:06 -0700	[thread overview]
Message-ID: <6f9d7066-9592-4a14-a811-c2451cbc33fa@quicinc.com> (raw)
In-Reply-To: <1acb74e5-e768-40f0-9eff-06b37c0d79ee@sirena.org.uk>

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

  reply	other threads:[~2024-06-05  0:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  0:16 Jeff Johnson
2024-06-04 11:56 ` Mark Brown
2024-06-04 13:59   ` Jeff Johnson
2024-06-04 14:14     ` Mark Brown
2024-06-05  0:02       ` Jeff Johnson [this message]
2024-06-04 14:46   ` Dan Carpenter
2024-06-04 15:00     ` Mark Brown
2024-06-04 19:20   ` Dragan Simic
2024-06-04 17:49 ` 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=6f9d7066-9592-4a14-a811-c2451cbc33fa@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bgoswami@quicinc.com \
    --cc=broonie@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kernel@quicinc.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tiwai@suse.com \
    /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

all inboxes | Powered by JetHome®