From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: wangyuquan <wangyuquan1236@phytium.com.cn>
Cc: <fan.ni@samsung.com>, <mst@redhat.com>,
<marcel.apfelbaum@gmail.com>, <qemu-devel@nongnu.org>,
<linux-cxl@vger.kernel.org>
Subject: Re: [RFC PATCH v3 1/2] hw/pxb-cxl: Rename the pxb cxl host bridge
Date: Fri, 25 Jul 2025 16:16:16 +0100 [thread overview]
Message-ID: <20250725161616.00007f09@huawei.com> (raw)
In-Reply-To: <20250617040649.81303-2-wangyuquan1236@phytium.com.cn>
On Tue, 17 Jun 2025 12:06:48 +0800
wangyuquan <wangyuquan1236@phytium.com.cn> wrote:
> This renames some descriptions and definitions of pxb cxl host
> bridge, since the original names can be confusing.
>
> Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
Fair enough.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> ---
> hw/pci-bridge/pci_expander_bridge.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/hw/pci-bridge/pci_expander_bridge.c b/hw/pci-bridge/pci_expander_bridge.c
> index 3a29dfefc2..bd637786d0 100644
> --- a/hw/pci-bridge/pci_expander_bridge.c
> +++ b/hw/pci-bridge/pci_expander_bridge.c
> @@ -201,7 +201,7 @@ static void pxb_cxl_realize(DeviceState *dev, Error **errp)
> }
>
> /*
> - * Host bridge realization has no means of knowning state associated
> + * PXB Host bridge realization has no means of knowning state associated
> * with a particular machine. As such, it is nececssary to delay
> * final setup of the host bridge register space until later in the
> * machine bring up.
> @@ -240,7 +240,7 @@ static void pxb_cxl_host_class_init(ObjectClass *class, const void *data)
> * This is a device to handle the MMIO for a CXL host bridge. It does nothing
> * else.
> */
> -static const TypeInfo cxl_host_info = {
> +static const TypeInfo pxb_cxl_host_info = {
> .name = TYPE_PXB_CXL_HOST,
> .parent = TYPE_PCI_HOST_BRIDGE,
> .instance_size = sizeof(CXLHost),
> @@ -522,7 +522,7 @@ static void pxb_cxl_dev_class_init(ObjectClass *klass, const void *data)
> * vendor, device, class, etc. ids are intentionally left out.
> */
>
> - dc->desc = "CXL Host Bridge";
> + dc->desc = "PXB CXL Host Bridge";
> device_class_set_props(dc, pxb_cxl_dev_properties);
> set_bit(DEVICE_CATEGORY_BRIDGE, dc->categories);
>
> @@ -549,7 +549,7 @@ static void pxb_register_types(void)
> type_register_static(&pxb_pcie_bus_info);
> type_register_static(&pxb_cxl_bus_info);
> type_register_static(&pxb_host_info);
> - type_register_static(&cxl_host_info);
> + type_register_static(&pxb_cxl_host_info);
> type_register_static(&pxb_dev_info);
> type_register_static(&pxb_pcie_dev_info);
> type_register_static(&pxb_cxl_dev_info);
next prev parent reply other threads:[~2025-07-25 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 4:06 [RFC PATCH v3 0/2] cxl: Support creation of a new CXL Host Bridge wangyuquan
2025-06-17 4:06 ` [RFC PATCH v3 1/2] hw/pxb-cxl: Rename the pxb cxl host bridge wangyuquan
2025-07-25 15:16 ` Jonathan Cameron via [this message]
2025-06-17 4:06 ` [RFC PATCH v3 2/2] pci-host/cxl: Support creation of a new CXL Host Bridge wangyuquan
2025-07-25 15:40 ` Jonathan Cameron via
2025-07-25 16:32 ` [RFC PATCH v3 0/2] cxl: " 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=20250725161616.00007f09@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=fan.ni@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=wangyuquan1236@phytium.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).