From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219966] modpost: EXPORT symbol "policy_has_boost_freq" [vmlinux] version generation failed, symbol will not be versioned.
Date: Sat, 05 Apr 2025 09:07:19 +0000 [thread overview]
Message-ID: <bug-219966-137361-oAAu7roBUR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219966-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219966
Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmenzel+bugzilla.kernel.org
| |@molgen.mpg.de
--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Thank you. I also get this, but I only with “6.15-rc0” and not with 6.14. In my
case, I bisected [1] the issue to commit 6a367577153a (percpu/x86:
enable strict percpu checks via named AS qualifiers) [2].
[1]:
https://lore.kernel.org/lkml/eb3c109f-550f-44ce-b0a1-3837aef1d02a@molgen.mpg.de/T/#u
[2]:
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a367577153acd9b432a5340fb10891eeb7e10f1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2025-04-05 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 19:04 [Bug 219966] New: modpost: EXPORT symbol "policy_has_boost_freq" [vmlinux] version generation failed, symbol will not be versioned bugzilla-daemon
2025-03-29 19:04 ` [Bug 219966] " bugzilla-daemon
2025-04-05 9:07 ` bugzilla-daemon [this message]
2025-04-06 6:51 ` bugzilla-daemon
2025-04-06 8:06 ` bugzilla-daemon
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=bug-219966-137361-oAAu7roBUR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).