All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tom Talpey <tom@talpey.com>,
	linux-cifs@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rosen Penev <rosenp@gmail.com>
Subject: Re: [PATCH] RFC: ksmbd: provide MODULE_VERSION()
Date: Sat, 31 May 2025 15:49:47 -0300	[thread overview]
Message-ID: <088096eba2d038bce2f73e6519d11ce9@manguebit.com> (raw)
In-Reply-To: <CAH2r5msU-45Up+BovgpwQ2eV5o5aRz+j+zh6jZLvn=ZsmNuNeQ@mail.gmail.com>

Steve French <smfrench@gmail.com> writes:

> It is interesting that almost 700 kernel modules define
> MODULE_VERSION() for their module, but only 4 filesystems (including
> cifs.ko).  I find it useful mainly for seeing which fixes are in
> (since some distros do 'full backports' so easier to look at the
> module version sometimes to see what fixes are likely in the module
> when someone reports a problem).   I am curious why few fs use it
> though since it is apparently very widely used for other module types.

I find cifs.ko version quite useless, especially for distro and stable
kernels which take fixes from newer versions while not backporting the
commit that bumps cifs.ko version.  So relying on that version becomes
pointless, IMO.

  reply	other threads:[~2025-05-31 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-31  6:42 [PATCH] RFC: ksmbd: provide MODULE_VERSION() Linus Walleij
2025-05-31  6:56 ` Greg Kroah-Hartman
2025-05-31 19:37   ` Linus Walleij
2025-05-31 17:50 ` Steve French
2025-05-31 18:49   ` Paulo Alcantara [this message]
2025-06-01  7:41     ` Greg Kroah-Hartman
2025-06-01 18:54       ` Linus Walleij
2025-06-01 19:18         ` Steve French
2025-06-02  5:34         ` Greg Kroah-Hartman
2025-06-01 19:56       ` Paulo Alcantara
2025-06-01 19:59         ` Steve French

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=088096eba2d038bce2f73e6519d11ce9@manguebit.com \
    --to=pc@manguebit.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linkinjeon@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=rosenp@gmail.com \
    --cc=senozhatsky@chromium.org \
    --cc=smfrench@gmail.com \
    --cc=tom@talpey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.