Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	SOUND ML <linux-sound@vger.kernel.org>,
	MEDIATEK ML <linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] ASoC: mt6660: delete MODULE_VERSION
Date: Wed, 4 Jun 2025 10:06:36 +0200	[thread overview]
Message-ID: <bcc1994c-6ece-4e71-a8b9-9367f6734381@gmail.com> (raw)
In-Reply-To: <bd02757e-458b-4a3c-9194-7d7bbbd318f5@sirena.org.uk>

On 6/2/25 1:21 PM, Mark Brown wrote:

> On Sat, May 31, 2025 at 05:59:49PM +0200, Xose Vazquez Perez wrote:
> 
> Why?

Reminiscent of ancient times when modules were developed outside the kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2cd53fa9d38b98ea5ae4268e021c4f4cd68227a5

This is the only driver under sound/ with this macro.

>> Cc: Liam Girdwood <lgirdwood@gmail.com>
>> Cc: Mark Brown <broonie@kernel.org>
>> Cc: Jaroslav Kysela <perex@perex.cz>
>> Cc: Takashi Iwai <tiwai@suse.com>
>> Cc: Matthias Brugger <matthias.bgg@gmail.com>
>> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> Cc: SOUND ML <linux-sound@vger.kernel.org>
>> Cc: MEDIATEK ML <linux-mediatek@lists.infradead.org>
>> ---
> 
> You've not provided a Signed-off-by for this so I can't do anything with
> it, please see Documentation/process/submitting-patches.rst for details
> on what this is and why it's important.

Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>

      reply	other threads:[~2025-06-04  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31 15:59 [PATCH] ASoC: mt6660: delete MODULE_VERSION Xose Vazquez Perez
2025-06-02 11:21 ` Mark Brown
2025-06-04  8:06   ` Xose Vazquez Perez [this message]

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=bcc1994c-6ece-4e71-a8b9-9367f6734381@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=perex@perex.cz \
    --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