[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKi4VA+14kihzGFbMT623BwMbZEzgYU6+jz8MpR9jqoC059oog@mail.gmail.com>
Date: Thu, 28 Mar 2019 10:41:59 -0700
From: Lucas De Marchi <lucas.de.marchi@...il.com>
To: Jessica Yu <jeyu@...nel.org>
Cc: Alexey Gladkov <gladkov.alexey@...il.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
linux-api@...r.kernel.org,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
Gleb Fotengauer-Malinovskiy <glebfm@...linux.org>,
"Dmitry V. Levin" <ldv@...linux.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-modules <linux-modules@...r.kernel.org>
Subject: Re: [RESEND PATCH v1] moduleparam: Save information about built-in
modules in separate file
On Wed, Mar 27, 2019 at 8:40 AM Jessica Yu <jeyu@...nel.org> 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.
Lucas De Marchi
Powered by blists - more mailing lists