From: Sasha Levin <sashal@kernel.org>
To: Cal Peake <cp@absolutedigital.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
jslaby@suse.cz, gregkh@linuxfoundation.org
Subject: Re: Linux 6.18.17 -- build regression
Date: Thu, 12 Mar 2026 20:43:51 -0400 [thread overview]
Message-ID: <abNdx_cQR_BqMm3z@laps> (raw)
In-Reply-To: <b1844e83-80a5-973e-93bd-9e721e27ebb@absolutedigital.net>
On Thu, Mar 12, 2026 at 06:24:19PM -0400, Cal Peake wrote:
>On Thu, 12 Mar 2026, Sasha Levin wrote:
>
>> I'm announcing the release of the 6.18.17 kernel.
>>
>> All users of the 6.18 kernel series must upgrade.
>>
>
>Hi,
>
>This release breaks my build with the following output:
>
> LD .tmp_vmlinux1
>ld: drivers/cxl/acpi.o: in function `add_root_nvdimm_bridge':
>acpi.c:(.text+0x16f): undefined reference to `devm_cxl_add_nvdimm_bridge'
>make[2]: *** [scripts/Makefile.vmlinux:72: vmlinux.unstripped] Error 1
>make[1]: *** [/home/cal/linux/kernel/build/linux-6.18.17/Makefile:1242: vmlinux] Error 2
>make: *** [Makefile:248: __sub-make] Error 2
>
>I've attached my gzipped config. Commit af9bf9889663 looks possibly
>guilty, but I don't have time at the moment to fully verify.
>
>Please let me know if I can provide anything else.
Hey,
Thanks for the report!
Could you please confirm that cherry-picking 93d0fcdddc9e ("cxl/acpi: Fix
CXL_ACPI and CXL_PMEM Kconfig tristate mismatch") fixes the issue you're
seeing?
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-13 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 11:24 Linux 6.18.17 Sasha Levin
2026-03-12 11:24 ` Sasha Levin
2026-03-12 22:24 ` Linux 6.18.17 -- build regression Cal Peake
2026-03-13 0:43 ` Sasha Levin [this message]
2026-03-13 22:04 ` Richard Narron
2026-03-13 22:40 ` Cal Peake
2026-03-14 15:00 ` Richard Narron
2026-03-13 22:20 ` Cal Peake
2026-03-13 23:30 ` Sasha Levin
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=abNdx_cQR_BqMm3z@laps \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cp@absolutedigital.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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