public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the bitmap tree
Date: Thu, 30 Apr 2026 11:11:12 +0200	[thread overview]
Message-ID: <20260430091113.4086100-1-thierry.reding@kernel.org> (raw)

Hi all,

After merging the bitmap tree, today's linux-next build (x86_64
allnoconfig) failed like this:

    ld: arch/x86/events/intel/core.o: in function `intel_hybrid_get_attr_cpus':
    core.c:(.text+0x944): undefined reference to `cpumap_print_to_pagebuf'
    ld: kernel/events/core.o: in function `cpumask_show':
    core.c:(.text+0xcb8): undefined reference to `cpumap_print_to_pagebuf'
    ld: drivers/base/cpu.o: in function `show_cpus_attr':
    cpu.c:(.text+0x280): undefined reference to `cpumap_print_to_pagebuf'

Caused by commit

    6d3a0b07f271 ("cpumask: switch cpumap_print_to_pagebuf() to using scnprintf()")

This seems to be caused by the new function not being available for
!CONFIG_SMP configurations, whereas previously it was a static inline
function and hence present irrespective of configuration.

I've fixed this up for today by reverting the following patches:

    af327141d0dd ("bitmap: drop bitmap_print_to_pagebuf()")
    6d3a0b07f271 ("cpumask: switch cpumap_print_to_pagebuf() to using scnprintf()")

Please fix this properly in the bitmap tree.

Thierry

             reply	other threads:[~2026-04-30  9:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  9:11 Thierry Reding [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-24 15:11 linux-next: build failure after merge of the bitmap tree Mark Brown
2026-03-24 17:56 ` Yury Norov
2025-11-25  7:24 Stephen Rothwell
2025-11-25  8:05 ` Geert Uytterhoeven
2025-11-25  8:31   ` Miquel Raynal
2025-11-25  8:37     ` Geert Uytterhoeven
2025-11-25 14:44       ` Yury Norov
2025-11-25 14:55         ` Miquel Raynal
2025-11-25  8:53     ` Miquel Raynal
2025-11-28  8:17   ` Miquel Raynal
2025-02-18  5:07 Stephen Rothwell
2025-02-18 10:35 ` Beata Michalska
2025-02-18 13:49   ` Stephen Rothwell
2025-02-18 14:10     ` Catalin Marinas
2025-02-18 14:16       ` Yury Norov
2025-02-18 18:23         ` Catalin Marinas
2025-02-18 19:28           ` Beata Michalska
2025-02-18 19:44             ` Catalin Marinas
2024-05-08  6:27 Stephen Rothwell
2024-05-08 13:24 ` Kuan-Wei Chiu
2024-05-08 22:18   ` Yury Norov
2023-10-20  4:49 Stephen Rothwell
2023-10-19  6:01 Stephen Rothwell
2023-10-19 15:58 ` Yury Norov
2023-10-20  4:24   ` Yury Norov
2023-10-20  4:51     ` Stephen Rothwell
2023-10-20 12:33       ` Yury Norov
2023-11-02 11:41         ` Alexander Lobakin
2022-09-26 23:53 broonie
2022-09-27  0:37 ` Yury Norov
2022-09-27 18:56   ` Mark Brown
2022-09-20  8:08 Stephen Rothwell
2022-09-20 14:49 ` Yury Norov
2022-07-27 10:29 Stephen Rothwell
2022-07-22  9:16 Stephen Rothwell
2022-07-22 19:29 ` Yury Norov
2022-07-15 10:29 Stephen Rothwell
2022-07-08  7:47 Stephen Rothwell
2022-05-02  8:15 Stephen Rothwell
2022-04-19  4:29 Stephen Rothwell

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=20260430091113.4086100-1-thierry.reding@kernel.org \
    --to=thierry.reding@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=yury.norov@gmail.com \
    /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