sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2 0/4] PCI: Simplify bus range parsing
Date: Wed, 15 Jan 2025 15:29:18 -0600	[thread overview]
Message-ID: <20250115212918.GA555721@bhelgaas> (raw)
In-Reply-To: <20250113231557.441289-1-helgaas@kernel.org>

On Mon, Jan 13, 2025 at 05:15:53PM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
> 
> Unexport of_pci_parse_bus_range() since it's only used in drivers/pci/of.c.
> 
> Drop the "No bus range found" message since host bridges typically lead to
> [bus 00-ff], and we already default to that if there is no "bus-range" DT
> property, so there's no point in requiring it in DT or complaining if it's
> not there.
> 
> Drop bus range parameters from devm_of_pci_get_host_bridge_resources()
> since they're always the same values.
> 
> Update a sparc comment that referred to of_pci_get_host_bridge_resources(),
> which no longer exists.
> 
> Bjorn Helgaas (4):
>   PCI: Unexport of_pci_parse_bus_range()
>   PCI: of: Drop 'No bus range found' message
>   PCI: of: Simplify devm_of_pci_get_host_bridge_resources() interface
>   sparc/PCI: Update reference to devm_of_pci_get_host_bridge_resources()
> 
>  arch/sparc/kernel/pci_common.c |  2 +-
>  drivers/pci/of.c               | 22 ++++++++++------------
>  drivers/pci/pci.h              |  7 -------
>  3 files changed, 11 insertions(+), 20 deletions(-)

Applied to pci/of for v6.14.

> Changes since v1
> (https://lore.kernel.org/r/20250103213129.5182-1-helgaas@kernel.org):
>   - Fix compile error
>   - Drop 'No bus range found' message
>   - Add Ack from Andreas for the sparc/PCI comment update
>   - Add Reviewed-by from Rob for the unexport patch

      parent reply	other threads:[~2025-01-15 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 23:15 [PATCH v2 0/4] PCI: Simplify bus range parsing Bjorn Helgaas
2025-01-13 23:15 ` [PATCH v2 1/4] PCI: Unexport of_pci_parse_bus_range() Bjorn Helgaas
2025-01-15  0:31   ` Sathyanarayanan Kuppuswamy
2025-01-13 23:15 ` [PATCH v2 2/4] PCI: of: Drop 'No bus range found' message Bjorn Helgaas
2025-01-15  0:31   ` Sathyanarayanan Kuppuswamy
2025-01-13 23:15 ` [PATCH v2 3/4] PCI: of: Simplify devm_of_pci_get_host_bridge_resources() interface Bjorn Helgaas
2025-01-15  0:21   ` Sathyanarayanan Kuppuswamy
2025-01-15 21:28     ` Bjorn Helgaas
2025-01-13 23:15 ` [PATCH v2 4/4] sparc/PCI: Update reference to devm_of_pci_get_host_bridge_resources() Bjorn Helgaas
2025-01-15  0:34   ` Sathyanarayanan Kuppuswamy
2025-01-15 21:29 ` Bjorn Helgaas [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=20250115212918.GA555721@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andreas@gaisler.com \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sparclinux@vger.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;
as well as URLs for NNTP newsgroup(s).