From: Keith Busch <kbusch@kernel.org>
To: Gregory Price <gourry@gourry.net>
Cc: Keith Busch <kbusch@meta.com>,
linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
dave.jiang@intel.com
Subject: Re: [PATCH] cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch
Date: Thu, 5 Mar 2026 16:26:04 -0700 [thread overview]
Message-ID: <aaoRDKvC2aVlECTJ@kbusch-mbp> (raw)
In-Reply-To: <aaoKBqP6pzAeF96q@gourry-fedora-PF4VCD3F>
On Thu, Mar 05, 2026 at 05:56:06PM -0500, Gregory Price wrote:
> > Anyway, my proposal here should force demotion to "m" for CXL_ACPI if
> > PMEM is also "m", where your proposal should force a failure path at
> > compile time if ACPI=y and PMEM=m. I really don't know if there's any
> > preference at all, I also just wanted the kernel build to complete
> > successfuly. :)
>
> my proposal allows compilation but fails during probe because the symbol
> is IS_REACHABLE()=false, but yeah, i have no idea what we want here.
Indeed, I didn't mean to suggest your solution may not build. I only
mean the forced runtime error path was decided at compile time. And I'm
totally okay with doing that if it's preferred over forcing module
demotion.
next prev parent reply other threads:[~2026-03-05 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 20:40 [PATCH] cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch Keith Busch
2026-03-05 22:12 ` Gregory Price
2026-03-05 22:43 ` Keith Busch
2026-03-05 22:56 ` Gregory Price
2026-03-05 23:26 ` Keith Busch [this message]
2026-03-06 1:07 ` dan.j.williams
2026-03-06 1:26 ` Keith Busch
2026-03-06 1:55 ` dan.j.williams
2026-03-06 10:50 ` Jonathan Cameron
2026-03-06 15:23 ` Dave Jiang
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=aaoRDKvC2aVlECTJ@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=kbusch@meta.com \
--cc=linux-cxl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.