From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-modules@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Aaron Tomlin <atomlin@atomlin.com>,
Shyam Saini <shyamsaini@linux.microsoft.com>,
Kees Cook <kees@kernel.org>,
Thorsten Blum <thorsten.blum@linux.dev>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] module: remove MODULE_VERSION()
Date: Sat, 14 Mar 2026 11:22:22 +0100 [thread overview]
Message-ID: <f036410e-f53c-4284-b108-18bcdb2f0d28@kernel.org> (raw)
In-Reply-To: <2026031303-prelaunch-creation-3fce@gregkh>
Le 13/03/2026 à 16:46, Greg Kroah-Hartman a écrit :
> On Fri, Mar 13, 2026 at 03:20:42PM +0100, Greg Kroah-Hartman wrote:
>> Module "versions" do not make sense as the kernel is built all at once,
>> the "version" is the overall kernel version number, so modules can not
>> really be described as having a unique version given that they rely on
>> the infrastructure of the whole kernel.
>>
>> For now, just make this an "empty" define, to keep existing code
>> building properly as the tree is slowly purged of the use of this over
>> time.
>>
>> This macro will be removed entirely in the future when there are no
>> in-tree users.
>>
>> Cc: Luis Chamberlain <mcgrof@kernel.org>
>> Cc: Petr Pavlu <petr.pavlu@suse.com>
>> Cc: Daniel Gomez <da.gomez@kernel.org>
>> Cc: Sami Tolvanen <samitolvanen@google.com>
>> Cc: Aaron Tomlin <atomlin@atomlin.com>
>> Cc: Shyam Saini <shyamsaini@linux.microsoft.com>
>> Cc: Kees Cook <kees@kernel.org>
>> Cc: Thorsten Blum <thorsten.blum@linux.dev>
>> Cc: Christoph Hellwig <hch@infradead.org>
>> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>> include/linux/module.h | 56 +++++++++---------------------------------
>> kernel/params.c | 30 ----------------------
>> 2 files changed, 11 insertions(+), 75 deletions(-)
>
>
> Sami just pointed out to me off-list that maybe I should also drop the
> srcversion stuff too. I'll gladly do that too, does anyone know if
> anyone even uses that anymore?
If I understand correctly the text in kernel/module/Kconfig, srcversion
is added only for modules which contain a MODULE_VERSION.
So as you drop MODULE_VERSION, srcversion becomes completely useless
doesn't it ?
Christophe
next prev parent reply other threads:[~2026-03-14 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 14:20 [PATCH] module: remove MODULE_VERSION() Greg Kroah-Hartman
2026-03-13 15:46 ` Greg Kroah-Hartman
2026-03-13 17:28 ` Sami Tolvanen
2026-03-14 10:22 ` Christophe Leroy (CS GROUP) [this message]
2026-03-16 8:58 ` Christoph Hellwig
2026-03-16 17:25 ` Sami Tolvanen
2026-03-16 10:48 ` Petr Pavlu
2026-03-13 17:07 ` Sami Tolvanen
2026-03-16 8:57 ` Christoph Hellwig
2026-03-16 9:37 ` Petr Pavlu
2026-03-16 10:03 ` Greg Kroah-Hartman
2026-03-17 12:50 ` Petr Pavlu
2026-03-27 12:27 ` Nam Cao
2026-03-27 12:44 ` Greg Kroah-Hartman
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=f036410e-f53c-4284-b108-18bcdb2f0d28@kernel.org \
--to=chleroy@kernel.org \
--cc=atomlin@atomlin.com \
--cc=da.gomez@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=shyamsaini@linux.microsoft.com \
--cc=thorsten.blum@linux.dev \
/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