From: Hanjun Guo <guohanjun@huawei.com>
To: Jeremy Linton <jeremy.linton@arm.com>, <linux-acpi@vger.kernel.org>
Cc: lorenzo.pieralisi@arm.com, linux-pci@vger.kernel.org,
tn@semihalf.com, rjw@rjwysocki.net, steven.price@arm.com,
sudeep.holla@arm.com, bhelgaas@google.com,
linux-arm-kernel@lists.infradead.org, lenb@kernel.org
Subject: Re: [PATCH v2] PCI/ACPI: Suppress missing MCFG message
Date: Wed, 9 Sep 2020 08:59:59 +0800 [thread overview]
Message-ID: <f7d5522a-9e44-236e-ad9f-44d3fd5c5ade@huawei.com> (raw)
In-Reply-To: <20200908210359.569294-1-jeremy.linton@arm.com>
On 2020/9/9 5:03, Jeremy Linton wrote:
> MCFG is an optional ACPI table. Given there are machines
> without PCI(e) (or it is hidden) we have been receiving
> queries/complaints about what this message means given
> its being presented as an error.
>
> Lets reduce the severity, the ACPI table list printed at
> boot will continue to provide another way to detect when
> the table is missing.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> ---
> drivers/acpi/pci_mcfg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/pci_mcfg.c b/drivers/acpi/pci_mcfg.c
> index 54b36b7ad47d..c8ef3bb5aa00 100644
> --- a/drivers/acpi/pci_mcfg.c
> +++ b/drivers/acpi/pci_mcfg.c
> @@ -280,5 +280,5 @@ void __init pci_mmcfg_late_init(void)
> {
> int err = acpi_table_parse(ACPI_SIG_MCFG, pci_mcfg_parse);
> if (err)
> - pr_err("Failed to parse MCFG (%d)\n", err);
> + pr_debug("Failed to parse MCFG (%d)\n", err);
> }
>
Reviewed-by: Hanjun Guo <guohanjun@huawei.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-09 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 21:03 [PATCH v2] PCI/ACPI: Suppress missing MCFG message Jeremy Linton
2020-09-09 0:59 ` Hanjun Guo [this message]
2020-09-09 14:42 ` 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=f7d5522a-9e44-236e-ad9f-44d3fd5c5ade@huawei.com \
--to=guohanjun@huawei.com \
--cc=bhelgaas@google.com \
--cc=jeremy.linton@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--cc=tn@semihalf.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