From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] ACPI: APEI: remove_quirk_mcfg_res() can be static
Date: Thu, 28 Oct 2021 06:46:22 +0800 [thread overview]
Message-ID: <20211027224622.GA6413@23a2bd086a91> (raw)
In-Reply-To: <20211027081312.53682-1-xuesong.chen@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
drivers/acpi/apei/apei-base.c:453:5: warning: symbol 'remove_quirk_mcfg_res' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
apei-base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/apei/apei-base.c b/drivers/acpi/apei/apei-base.c
index 4f7311a55a342..dbb0fa4125e32 100644
--- a/drivers/acpi/apei/apei-base.c
+++ b/drivers/acpi/apei/apei-base.c
@@ -450,7 +450,7 @@ static int apei_get_nvs_resources(struct apei_resources *resources)
}
#ifdef CONFIG_PCI
-int remove_quirk_mcfg_res(struct apei_resources *mcfg_res)
+static int remove_quirk_mcfg_res(struct apei_resources *mcfg_res)
{
#ifdef CONFIG_PCI_QUIRKS
int rc = 0;
next prev parent reply other threads:[~2021-10-27 22:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 4:49 [PATCH v3 0/2] PCI MCFG consolidation and APEI resource filterin Xuesong Chen
2021-10-19 4:49 ` Xuesong Chen
2021-10-19 15:12 ` Bjorn Helgaas
2021-10-19 15:12 ` Bjorn Helgaas
2021-10-20 2:28 ` Xuesong Chen
2021-10-20 2:28 ` Xuesong Chen
2021-10-27 8:10 ` [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering Xuesong Chen
2021-10-27 8:10 ` Xuesong Chen
2021-10-27 8:12 ` [PATCH v4 1/4] PCI: MCFG: Consolidate the separate PCI MCFG table entry list Xuesong Chen
2021-10-27 8:12 ` Xuesong Chen
2021-10-27 8:12 ` [PATCH v4 2/4] ACPI: APEI: Filter the PCI MCFG address with an arch-agnostic method Xuesong Chen
2021-10-27 8:12 ` Xuesong Chen
2021-10-27 8:13 ` [PATCH v4 3/4] ACPI: APEI: Reserve the MCFG address for quirk ECAM implementation Xuesong Chen
2021-10-27 8:13 ` Xuesong Chen
2021-10-27 22:46 ` kernel test robot
2021-10-27 22:46 ` kernel test robot
2021-10-27 22:46 ` kernel test robot
2021-11-01 17:15 ` Bjorn Helgaas
2021-11-01 17:15 ` Bjorn Helgaas
2021-11-04 2:30 ` [kbuild-all] " Rong Chen
2021-11-04 2:30 ` Rong Chen
2021-10-27 22:46 ` kernel test robot [this message]
2021-10-28 4:13 ` kernel test robot
2021-10-29 12:38 ` kernel test robot
2021-10-27 8:13 ` [PATCH v4 4/4] PCI: MCFG: Add the MCFG entry parse log message Xuesong Chen
2021-10-27 8:13 ` Xuesong Chen
2021-11-01 2:18 ` [PATCH v4 0/4] PCI MCFG consolidation and APEI resource filtering Xuesong Chen
2021-11-01 2:18 ` Xuesong Chen
2021-11-01 9:36 ` Will Deacon
2021-11-01 9:36 ` Will Deacon
2021-11-01 12:12 ` Xuesong Chen
2021-11-01 12:12 ` Xuesong Chen
2021-11-01 12:22 ` Borislav Petkov
2021-11-01 12:22 ` Borislav Petkov
2021-11-01 13:32 ` Xuesong Chen
2021-11-01 13:32 ` Xuesong Chen
2021-11-01 13:55 ` Borislav Petkov
2021-11-01 13:55 ` Borislav Petkov
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=20211027224622.GA6413@23a2bd086a91 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.