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 B1119234994; Fri, 27 Jun 2025 08:27:29 +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=1751012853; cv=none; b=FZWdbpaYYTYQ57IE4EexnZUGsKk+NlKL0hwDcuJPmqCEtJj7gAQaDMqmX2ABPYMgdlqnO7eLA74LsdDkRE8gWc0GTOmupY9IyGh64+H2X9plhB38WbpOgyxSxJ4Hw/alJqj7aPC6wHglMBFUZZQjdedJgj6OwwVtDf/EjutwGg8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1751012853; c=relaxed/simple; bh=gKAXUtnbU+Q8i7Yj/BtQIMcrqcxyWX69S3vrzYLhC2A=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=ZJOUGp6fGHPIBiDPJtatJOTOFQI14CAfvUn2Q+W6JHRUR8oAtNsaxWC6AbGmLLwfpt042wbmiZ4HqFyMEqAQphEN8RqaHg8zNXSfjeDWuhC61tEBDP7Oeiuk/XUTKOUwBFM+K+zAgBuFNKyNRTwCxbJWxu2N8odNKMx6dFFFqvw= 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.216]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4bT7v22P37z6M4rR; Fri, 27 Jun 2025 16:26:38 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id B47BF1402EC; Fri, 27 Jun 2025 16:27:26 +0800 (CST) Received: from localhost (10.48.153.213) 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; Fri, 27 Jun 2025 10:27:26 +0200 Date: Fri, 27 Jun 2025 09:27:24 +0100 From: Jonathan Cameron To: CC: , , , , , , , , , Alejandro Lucero Subject: Re: [PATCH v17 04/22] cxl: allow Type2 drivers to map cxl component regs Message-ID: <20250627092724.00004885@huawei.com> In-Reply-To: <20250624141355.269056-5-alejandro.lucero-palau@amd.com> References: <20250624141355.269056-1-alejandro.lucero-palau@amd.com> <20250624141355.269056-5-alejandro.lucero-palau@amd.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: netdev@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: lhrpeml100005.china.huawei.com (7.191.160.25) To frapeml500008.china.huawei.com (7.182.85.71) On Tue, 24 Jun 2025 15:13:37 +0100 alejandro.lucero-palau@amd.com wrote: > From: Alejandro Lucero > > Export cxl core functions for a Type2 driver being able to discover and > map the device component registers. > > Signed-off-by: Alejandro Lucero I'll see how this is used in later patches, but on it's own looks reasonable to me Reviewed-by: Jonathan Cameron