All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Paulo Alcantara <pc@manguebit.com>,
	Steve French <smfrench@gmail.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tom Talpey <tom@talpey.com>,
	linux-cifs@vger.kernel.org, Rosen Penev <rosenp@gmail.com>
Subject: Re: [PATCH] RFC: ksmbd: provide MODULE_VERSION()
Date: Mon, 2 Jun 2025 07:34:32 +0200	[thread overview]
Message-ID: <2025060254-unscathed-junior-1b43@gregkh> (raw)
In-Reply-To: <CACRpkdZ0w85ecgtjbiypG8K37eBF9hk-7oqSq8E9K6_+SE+nUQ@mail.gmail.com>

On Sun, Jun 01, 2025 at 08:54:10PM +0200, Linus Walleij wrote:
> On Sun, Jun 1, 2025 at 9:41 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Sat, May 31, 2025 at 03:49:47PM -0300, Paulo Alcantara wrote:
> > >  So relying on that version becomes
> > > pointless, IMO.
> >
> > Yes, it is pointless, which is why it really should just be removed.
> > I'll do a sweep of the tree after -rc1 is out and start sending out
> > patches...
> 
> In a way I'm happy with that result :D
> 
> But what do you think about the original problem of making
> the dir /sys/modules/foo appear for a compiled-in module?

It does that today, if the module has a parameter, right?  Maybe change
that to always do that even if there is no parameter present and see
what happens?

thanks,

greg k-h

  parent reply	other threads:[~2025-06-02  5:34 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
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 [this message]
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=2025060254-unscathed-junior-1b43@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linkinjeon@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.com \
    --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.