From: Petr Pavlu <petr.pavlu@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Shyam Saini <shyamsaini@linux.microsoft.com>
Subject: [GIT PULL] Modules fixes for v6.15-rc5
Date: Wed, 30 Apr 2025 15:12:11 +0200 [thread overview]
Message-ID: <223a3bc5-0696-4547-b6ca-ab6882510259@suse.com> (raw)
The following changes since commit 8ffd015db85fea3e15a77027fda6c02ced4d2444:
Linux 6.15-rc2 (2025-04-13 11:54:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git/ tags/modules-6.15-rc5
for you to fetch changes up to f95bbfe18512c5c018720468959edac056a17196:
drivers: base: handle module_kobject creation (2025-04-16 15:10:55 +0200)
----------------------------------------------------------------
Modules fixes for v6.15-rc5
A single series is present to properly handle the module_kobject creation.
It fixes a problem with missing /sys/module/<module>/drivers for built-in
modules.
The fix has been on linux-next for two weeks with no reported issues.
----------------------------------------------------------------
Shyam Saini (4):
kernel: param: rename locate_module_kobject
kernel: refactor lookup_or_create_module_kobject()
kernel: globalize lookup_or_create_module_kobject()
drivers: base: handle module_kobject creation
drivers/base/module.c | 13 +++++--------
include/linux/module.h | 2 ++
kernel/params.c | 47 ++++++++++++++++++++++-------------------------
3 files changed, 29 insertions(+), 33 deletions(-)
next reply other threads:[~2025-04-30 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 13:12 Petr Pavlu [this message]
2025-04-30 18:12 ` pr-tracker-bot
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=223a3bc5-0696-4547-b6ca-ab6882510259@suse.com \
--to=petr.pavlu@suse.com \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=samitolvanen@google.com \
--cc=shyamsaini@linux.microsoft.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®