public inbox for linux-kernel@vger.kernel.org
 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: [PATCH v2 2/4] PCI: of: Drop 'No bus range found' message
Date: Mon, 13 Jan 2025 17:15:55 -0600	[thread overview]
Message-ID: <20250113231557.441289-3-helgaas@kernel.org> (raw)
In-Reply-To: <20250113231557.441289-1-helgaas@kernel.org>

From: Bjorn Helgaas <bhelgaas@google.com>

The typical bus range for a host bridge is [bus 00-ff], and
devm_of_pci_get_host_bridge_resources() defaults to that unless DT contains
a "bus-range" property.

devm_of_pci_get_host_bridge_resources() previously emitted a message when
there was no "bus-range" property, but that seems unnecessary for this
common situation.  Remove the message.

Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
---
 drivers/pci/of.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/pci/of.c b/drivers/pci/of.c
index 2f579b691f8e..48b9274b846e 100644
--- a/drivers/pci/of.c
+++ b/drivers/pci/of.c
@@ -346,8 +346,6 @@ static int devm_of_pci_get_host_bridge_resources(struct device *dev,
 		bus_range->start = busno;
 		bus_range->end = bus_max;
 		bus_range->flags = IORESOURCE_BUS;
-		dev_info(dev, "  No bus range found for %pOF, using %pR\n",
-			 dev_node, bus_range);
 	} else {
 		if (bus_range->end > bus_range->start + bus_max)
 			bus_range->end = bus_range->start + bus_max;
-- 
2.34.1


  parent reply	other threads:[~2025-01-13 23:16 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 ` Bjorn Helgaas [this message]
2025-01-15  0:31   ` [PATCH v2 2/4] PCI: of: Drop 'No bus range found' message 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 ` [PATCH v2 0/4] PCI: Simplify bus range parsing Bjorn Helgaas

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=20250113231557.441289-3-helgaas@kernel.org \
    --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