From: Lizhi Hou <lizhi.hou@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Rob Herring <robh@kernel.org>
Cc: Andrea della Porta <andrea.porta@suse.com>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] PCI: of_property: Rename struct of_pci_range to of_pci_range_entry
Date: Fri, 17 Jan 2025 13:27:00 -0800 [thread overview]
Message-ID: <902a1886-c150-d77e-434c-b1a8816f7a29@amd.com> (raw)
In-Reply-To: <20250117161037.643953-1-helgaas@kernel.org>
On 1/17/25 08:10, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Previously there were two definitions of struct of_pci_range: one in
> include/linux/of_address.h and another local to drivers/pci/of_property.c.
>
> Rename the local struct of_pci_range to of_pci_range_entry to avoid
> confusion.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> drivers/pci/of_property.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/of_property.c b/drivers/pci/of_property.c
> index 886c236e5de6..58fbafac7c6a 100644
> --- a/drivers/pci/of_property.c
> +++ b/drivers/pci/of_property.c
> @@ -26,7 +26,7 @@ struct of_pci_addr_pair {
> * side and the child address is the corresponding address on the secondary
> * side.
> */
> -struct of_pci_range {
> +struct of_pci_range_entry {
> u32 child_addr[OF_PCI_ADDRESS_CELLS];
> u32 parent_addr[OF_PCI_ADDRESS_CELLS];
> u32 size[OF_PCI_SIZE_CELLS];
> @@ -101,7 +101,7 @@ static int of_pci_prop_bus_range(struct pci_dev *pdev,
> static int of_pci_prop_ranges(struct pci_dev *pdev, struct of_changeset *ocs,
> struct device_node *np)
> {
> - struct of_pci_range *rp;
> + struct of_pci_range_entry *rp;
> struct resource *res;
> int i, j, ret;
> u32 flags, num;
Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
prev parent reply other threads:[~2025-01-17 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 16:10 [PATCH] PCI: of_property: Rename struct of_pci_range to of_pci_range_entry Bjorn Helgaas
2025-01-17 21:27 ` Lizhi Hou [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=902a1886-c150-d77e-434c-b1a8816f7a29@amd.com \
--to=lizhi.hou@amd.com \
--cc=andrea.porta@suse.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
/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