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 9879B19DF7A; Thu, 21 Nov 2024 15:19:06 +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=1732202348; cv=none; b=RK52X0iScL9eJpNwOOo4wsj18JyK3uDVGSP0ljtQw/OcE9oguZ52ITLr04waZJkGOYwQsg2k/6KT7/IPRbvYwzMwaOdphPKQijzrF4j0WzY/hwV6CoZd02iwMnI3qrLs1WPsAtt1c2io1EIkrexMZKwI1T/WCrQye50EKQ9Oe5A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1732202348; c=relaxed/simple; bh=+cEizs5yzaKHeKN7Jw+NGs2P7eBMrxHMIJTfcbDGxZ8=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Od9Xk2wHizl9Wc0g5m1oZhnKfyg+wKYMFeYRMrX7iHZ/UMCYhEgPoJR8pXp3oj3ylhB2MJIUfBIpx7lJiGHvFf1JF34dfroookJkTuWa5Q96B85WN1YO1dTQi/8h8cVYgGgEIAZlbwV0Ze7ltcjbFpxrSfX3sIeucha8kNOIZXg= 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.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XvMJq6WRpz6J9qF; Thu, 21 Nov 2024 23:16:43 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id 0301C140133; Thu, 21 Nov 2024 23:19:04 +0800 (CST) Received: from localhost (10.203.177.66) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 21 Nov 2024 16:19:03 +0100 Date: Thu, 21 Nov 2024 15:19:01 +0000 From: Jonathan Cameron To: CC: , , , , , , , , , , , , , Subject: Re: [PATCH 04/13] rasdaemon: cxl: Update common event to CXL spec rev 3.1 Message-ID: <20241121151901.00005eff@huawei.com> In-Reply-To: <20241120095923.1891-5-shiju.jose@huawei.com> References: <20241120095923.1891-1-shiju.jose@huawei.com> <20241120095923.1891-5-shiju.jose@huawei.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: lhrpeml500005.china.huawei.com (7.191.163.240) To frapeml500008.china.huawei.com (7.182.85.71) On Wed, 20 Nov 2024 09:59:14 +0000 wrote: > From: Shiju Jose > > CXL spec 3.1 section 8.2.9.2.1 Table 8-42, Common Event Record format has > updated with Maintenance Operation Subclass information. > > Add updates in rasdaemon CXL event handler for the above spec change > and for the corresponding changes in kernel CXL common trace event > implementation. > > Signed-off-by: Shiju Jose LGTM Reviewed-by: Jonathan Cameron