public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dylan E." <dylan.eskew@candelatech.com>
To: Dave Jiang <dave.jiang@intel.com>,
	dave@stgolabs.net, jonathan.cameron@huawei.com,
	alison.schofield@intel.com, vishal.l.verma@intel.com,
	ira.weiny@intel.com, dan.j.williams@intel.com
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH] cxl: Add CXL_PMEM as dependency for CXL_ACPI
Date: Fri, 27 Mar 2026 06:27:01 -0700	[thread overview]
Message-ID: <7e8a5d33-9b5e-41a1-b431-afa8c63d2ee4@candelatech.com> (raw)
In-Reply-To: <594e2663-06ff-44c4-8420-f00b788290cc@intel.com>

> On 3/26/26 2:14 PM, dylan.eskew@candelatech.com wrote:
>> From: Dylan Eskew <dylan.eskew@candelatech.com>
>>
>> Prevent a linking issue against CXL_PMEM when CXL_ACPI is configured in
>> Kconfig.
>>
>> Signed-off-by: Dylan Eskew <dylan.eskew@candelatech.com>
> Hi Dylan, does this commit fixes your issue? It's in Linus's tree now.
> 93d0fcdddc9e ("cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch")

Hi Dave,

This looks to fix it, thanks! I was sitting at -rc5 not thinking there 
was anything farther up the tree.

>> ---
>>   drivers/cxl/Kconfig | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/cxl/Kconfig b/drivers/cxl/Kconfig
>> index 48b7314afdb8..baf1d17ec0fc 100644
>> --- a/drivers/cxl/Kconfig
>> +++ b/drivers/cxl/Kconfig
>> @@ -58,6 +58,7 @@ config CXL_ACPI
>>   	tristate "CXL ACPI: Platform Support"
>>   	depends on ACPI
>>   	depends on ACPI_NUMA
>> +	depends on CXL_PMEM
>>   	default CXL_BUS
>>   	select ACPI_TABLE_LIB
>>   	select ACPI_HMAT

      reply	other threads:[~2026-03-27 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 21:14 [PATCH] cxl: Add CXL_PMEM as dependency for CXL_ACPI dylan.eskew
2026-03-26 21:32 ` Dave Jiang
2026-03-27 13:27   ` Dylan E. [this message]

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=7e8a5d33-9b5e-41a1-b431-afa8c63d2ee4@candelatech.com \
    --to=dylan.eskew@candelatech.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=vishal.l.verma@intel.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