From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
samitolvanen@google.com, petr.pavlu@suse.com,
da.gomez@samsung.com, linux-modules@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
geert@linux-m68k.org, masahiroy@kernel.org, mmaurer@google.com,
arnd@arndb.de, deller@gmx.de, song@kernel.org
Subject: [GIT PULL] Modules fixes for v6.13-rc1
Date: Thu, 28 Nov 2024 11:27:00 -0800 [thread overview]
Message-ID: <Z0jEBLLRoUKoBVPk@bombadil.infradead.org> (raw)
The following changes since commit b86545e02e8c22fb89218f29d381fa8e8b91d815:
Merge tag 'acpi-6.13-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2024-11-27 14:50:31 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git/ tags/modules-6.13-rc1-v2
for you to fetch changes up to c5efad88a94613cf60fed010b96dbc3044389316:
selftests: find_symbol: Actually use load_mod() parameter (2024-11-28 11:17:38 -0800)
----------------------------------------------------------------
Modules fixes for v6.13-rc1
This consists of 3 fixes, the main one build that we build the kallsyms
test modules all over again if we just run make twice.
----------------------------------------------------------------
Geert Uytterhoeven (1):
selftests: find_symbol: Actually use load_mod() parameter
Luis Chamberlain (2):
selftests: kallsyms: fix double build stupidity
selftests: kallsyms: fix and clarify current test boundaries
lib/Kconfig.debug | 32 ++++++++++++++++++++++++++-
lib/tests/module/Makefile | 17 +++++++-------
lib/tests/module/gen_test_kallsyms.sh | 9 ++++++--
tools/testing/selftests/module/find_symbol.sh | 4 ++--
4 files changed, 48 insertions(+), 14 deletions(-)
next reply other threads:[~2024-11-28 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 19:27 Luis Chamberlain [this message]
2024-11-29 19:18 ` Linus Torvalds
2024-11-29 19:20 ` 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=Z0jEBLLRoUKoBVPk@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=arnd@arndb.de \
--cc=da.gomez@samsung.com \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mmaurer@google.com \
--cc=patches@lists.linux.dev \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=song@kernel.org \
--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®