From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: LinuxPPC-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/6] 44x/pci: Continue pci setup even if there is no sdr-base in the device-tree
Date: Wed, 30 Nov 2011 16:46:13 +1100 [thread overview]
Message-ID: <1322631973.21641.42.camel@pasglop> (raw)
In-Reply-To: <1322630640-13708-2-git-send-email-tony@bakeyournoodle.com>
On Wed, 2011-11-30 at 16:23 +1100, Tony Breeds wrote:
> Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> ---
> arch/powerpc/sysdev/ppc4xx_pci.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/sysdev/ppc4xx_pci.c b/arch/powerpc/sysdev/ppc4xx_pci.c
> index 16f5eba..d3fa380 100644
> --- a/arch/powerpc/sysdev/ppc4xx_pci.c
> +++ b/arch/powerpc/sysdev/ppc4xx_pci.c
> @@ -1974,11 +1974,11 @@ static void __init ppc4xx_probe_pciex_bridge(struct device_node *np)
> port->node = of_node_get(np);
> pval = of_get_property(np, "sdr-base", NULL);
> if (pval == NULL) {
> - printk(KERN_ERR "PCIE: missing sdr-base for %s\n",
> + printk(KERN_INFO "PCIE: missing sdr-base for %s\n",
> np->full_name);
If you don't expect an sdr-base as part of the normal operations of that
bridge, don't bring a message that makes me think something is wrong :-)
Just changing the severity isn't enough. you should just remove the
message and later on, print/warn/error out if you decide you actually
need an sdr-base (such as in the backend).
Cheers,
Ben.
> - return;
> + } else {
> + port->sdr_base = *pval;
> }
> - port->sdr_base = *pval;
>
> /* Check if device_type property is set to "pci" or "pci-endpoint".
> * Resulting from this setup this PCIe port will be configured
next prev parent reply other threads:[~2011-11-30 5:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 5:23 Add support for the currituck 476 platform from IBM Tony Breeds
2011-11-30 5:23 ` [PATCH 1/6] 44x/pci: Continue pci setup even if there is no sdr-base in the device-tree Tony Breeds
2011-11-30 5:46 ` Benjamin Herrenschmidt [this message]
2011-12-01 1:11 ` Tony Breeds
2011-11-30 5:23 ` [PATCH 2/6] 44x/pci: Setup the dma_window properties for each pci_controller Tony Breeds
2011-11-30 5:23 ` [PATCH 3/6] 44x: Removing dead CONFIG_PPC47x Tony Breeds
2011-11-30 11:43 ` Josh Boyer
2011-11-30 20:20 ` Benjamin Herrenschmidt
2011-11-30 5:23 ` [PATCH 4/6] powerpc/boot: Add extended precision shifts to the boot wrapper Tony Breeds
2011-11-30 5:48 ` Benjamin Herrenschmidt
2011-11-30 11:45 ` Josh Boyer
2011-11-30 20:21 ` Benjamin Herrenschmidt
2011-11-30 20:28 ` Scott Wood
2011-11-30 23:25 ` Tony Breeds
2011-11-30 5:23 ` [PATCH 5/6] powerpc/boot: Add mfdcrx Tony Breeds
2011-11-30 13:09 ` Segher Boessenkool
2011-11-30 18:10 ` David Laight
2011-12-01 22:55 ` Segher Boessenkool
2011-11-30 23:30 ` Tony Breeds
2011-11-30 23:35 ` Tony Breeds
2011-11-30 5:24 ` [PATCH 6/6] 44x/currituck: Add support for the new IBM currituck platform Tony Breeds
2011-11-30 6:20 ` Benjamin Herrenschmidt
2011-11-30 6:31 ` David Gibson
2011-12-01 4:05 ` Tony Breeds
2011-12-01 4:29 ` Tony Breeds
2011-11-30 13:23 ` Kumar Gala
2011-12-01 4:16 ` Tony Breeds
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=1322631973.21641.42.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tony@bakeyournoodle.com \
/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).