Linux-Modules Archive on
 help / color / Atom feed
From: Greg KH <>
To: Lucas De Marchi <>
Cc: Jessica Yu <>,
	Alexey Gladkov <>,
	Masahiro Yamada <>,
	Michal Marek <>,
	Linux Kernel Mailing List <>,
	Linux Kbuild mailing list <>,,
	"Kirill A . Shutemov" <>,
	Gleb Fotengauer-Malinovskiy <>,
	"Dmitry V. Levin" <>,
	Dmitry Torokhov <>,
	Rusty Russell <>,
	linux-modules <>
Subject: Re: [RESEND PATCH v1] moduleparam: Save information about built-in modules in separate file
Date: Thu, 28 Mar 2019 19:45:46 +0100
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Mar 28, 2019 at 10:41:59AM -0700, Lucas De Marchi wrote:
> On Wed, Mar 27, 2019 at 8:40 AM Jessica Yu <> wrote:
> > >No. There are definitely not all modules. I have a builtin sha256_generic,
> > >but I can't find him in the /sys/module.
> >
> > Yeah, you'll only find builtin modules under /sys/module/ if it has any module
> > parameters, otherwise you won't find it there. As Masahiro already mentioned,
> > if a builtin module has any parameters, they would be accessible under /sys/module/.
> Could we please change that and add the sysfs entry regardless of
> what's being discussed here? Not having the entry there simply because
> we don't have parameters for that module always annoyed me.

What is the sysfs directory going to show?  Will it just be empty?

Feel free to send a patch for this, but from what I remember, it wasn't
the easiest thing to do for some reason.  But given that the code was
implemented before git was, I can't quite remember.


greg k-h

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190315101013.GN8455@Legion-PC.fortress>
     [not found] ` <>
     [not found]   ` <20190326172411.GA15936@Legion-PC.fortress>
     [not found]     ` <20190327154025.GB23293@linux-8ccs>
2019-03-28 17:41       ` Lucas De Marchi
2019-03-28 18:45         ` Greg KH [this message]
2019-03-28 21:33           ` Dmitry Torokhov

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Modules Archive on

Archives are clonable:
	git clone --mirror linux-modules/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-modules linux-modules/ \
	public-inbox-index linux-modules

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox