From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 652D72FFF9D; Wed, 14 Jan 2026 19:12:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768417980; cv=none; b=K606AgadOq994SyJqw6FqiNeNc8bNHnJnFr6AbDV03Ukr9J3UoAuaxgZFpfquhe81pRiat8ngY+c0qsXMxOK+IpvYCvzxLUJtylCwHvpyZOhXnuN6O0uQ4mneuVVgrqwcA4qiIQejoY+0q1varugpKnsARSWJQzgUBXiFG26G7A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768417980; c=relaxed/simple; bh=V8c9TblLKgLoEbA0THl/j4YKjEy2OuUJTdIiuvNUegc=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=MWCN2LSTCo5IfGoayu7TXQbh+wIkUAtTpCprweCSC48QWRo60KsPEb6iB4lfNrDIAaZaHqZsmJQmiT2y4p60KxSla8XQbtOTcRujsaQgAAIJNWOABpESh3YSEaSMOIcdTWOpsEO7D/ydn06k/QqNJN27NCdppeCH+eCgb51cfRM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.224.107]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4drwjj2JKDzJ469d; Thu, 15 Jan 2026 03:12:41 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id 6573F40570; Thu, 15 Jan 2026 03:12:56 +0800 (CST) Received: from localhost (10.203.177.15) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Wed, 14 Jan 2026 19:12:55 +0000 Date: Wed, 14 Jan 2026 19:12:54 +0000 From: Jonathan Cameron To: Terry Bowman CC: , , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH v14 13/34] PCI/AER: Replace PCIEAER_CXL symbol with CXL_RAS Message-ID: <20260114191254.00007f0a@huawei.com> In-Reply-To: <20260114182055.46029-14-terry.bowman@amd.com> References: <20260114182055.46029-1-terry.bowman@amd.com> <20260114182055.46029-14-terry.bowman@amd.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml500009.china.huawei.com (7.191.174.84) To dubpeml100005.china.huawei.com (7.214.146.113) On Wed, 14 Jan 2026 12:20:34 -0600 Terry Bowman wrote: > From: Dan Williams > > One of the primary reasons for the CXL driver to exist is to perform error > handling. If both PCIEAER and CXL are enabled then light up CXL error > handling as well. The work to remove CONFIG_PCIEAER_CXL started in: > > commit 4ae6ae66649c ("cxl/pci: Remove CXL VH handling in CONFIG_PCIEAER_CXL conditional blocks from core/pci.c") > > Finish that off with conditionally compiling all CXL RAS related helpers > with CONFIG_CXL_RAS. > > Signed-off-by: Dan Williams > Reviewed-by: Terry Bowman Reviewed-by: Jonathan Cameron