From: Jiang Liu <jiang.liu@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
Don Dutile <ddutile@redhat.com>
Cc: Jiang Liu <jiang.liu@huawei.com>,
Yijing Wang <wangyijing@huawei.com>,
Keping Chen <chenkeping@huawei.com>, <linux-pci@vger.kernel.org>,
Jiang Liu <liuj97@gmail.com>
Subject: [PATCH v8 09/12] x86/PCI: get rid of redundant log messages
Date: Tue, 19 Jun 2012 21:15:29 +0800 [thread overview]
Message-ID: <1340111732-6276-10-git-send-email-jiang.liu@huawei.com> (raw)
In-Reply-To: <1340111732-6276-1-git-send-email-jiang.liu@huawei.com>
For each resource of a PCI host bridge, the arch code and PCI
code log following messages:
"pci_root PNP0A08:00: host bridge window [io 0x0000-0x03af]",
"pci_bus 0000:00: root bus resource [io 0x0000-0x03af]"
Signed-off-by: Jiang Liu <liuj97@gmail.com>
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
---
arch/x86/pci/acpi.c | 7 -------
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
index 4e0ed1e..e72e412 100644
--- a/arch/x86/pci/acpi.c
+++ b/arch/x86/pci/acpi.c
@@ -295,13 +295,6 @@ setup_resource(struct acpi_resource *acpi_res, void *data)
}
info->res_num++;
- if (addr.translation_offset)
- dev_info(&info->bridge->dev, "host bridge window %pR "
- "(PCI address [%#llx-%#llx])\n",
- res, res->start - addr.translation_offset,
- res->end - addr.translation_offset);
- else
- dev_info(&info->bridge->dev, "host bridge window %pR\n", res);
return AE_OK;
}
--
1.7.1
next prev parent reply other threads:[~2012-06-19 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 13:15 [PATCH v8 00/12] PCI, x86: update MMCFG information when hot-plugging PCI host bridges Jiang Liu
2012-06-19 13:15 ` [PATCH v8 01/12] x86/PCI: split out pci_mmcfg_check_reserved() for code reuse Jiang Liu
2012-06-19 13:15 ` [PATCH v8 02/12] x86/PCI: split out pci_mmconfig_alloc() " Jiang Liu
2012-06-19 13:15 ` [PATCH v8 03/12] x86/PCI: use RCU list to protect mmconfig list Jiang Liu
2012-06-19 13:15 ` [PATCH v8 04/12] x86/PCI: introduce pci_mmcfg_arch_map()/pci_mmcfg_arch_unmap() Jiang Liu
2012-06-19 13:15 ` [PATCH v8 05/12] x86/PCI: add pci_mmconfig_insert()/delete() for PCI root bridge hotplug Jiang Liu
2012-06-19 13:15 ` [PATCH v8 06/12] PCI/ACPI: provide MCFG address for PCI host bridges Jiang Liu
2012-06-19 18:34 ` Yinghai Lu
2012-06-20 8:32 ` Jiang Liu
2012-06-20 18:03 ` Yinghai Lu
2012-06-21 1:36 ` Jiang Liu
2012-06-19 13:15 ` [PATCH v8 07/12] x86/PCI: update MMCFG information when hot-plugging " Jiang Liu
2012-06-19 13:15 ` [PATCH v8 08/12] x86/PCI: simplify pci_mmcfg_late_insert_resources() Jiang Liu
2012-06-19 13:15 ` Jiang Liu [this message]
2012-06-19 13:15 ` [PATCH v8 10/12] x86/PCI: refine __pci_mmcfg_init() for better code readability Jiang Liu
2012-06-19 18:31 ` Yinghai Lu
2012-06-20 8:50 ` Jiang Liu
2012-06-19 13:15 ` [PATCH v8 11/12] ACPI: mark acpi_sfi_table_parse() as __init Jiang Liu
2012-06-19 13:15 ` [RFC PATCH v8 12/12] x86/PCI: add MMCFG information on demand Jiang Liu
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=1340111732-6276-10-git-send-email-jiang.liu@huawei.com \
--to=jiang.liu@huawei.com \
--cc=bhelgaas@google.com \
--cc=chenkeping@huawei.com \
--cc=ddutile@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=wangyijing@huawei.com \
--cc=yinghai@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).