From: kbuild test robot <fengguang.wu@intel.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: kbuild-all@01.org, linux-pci@vger.kernel.org
Subject: [RFC PATCH pci] PCI/AER: aer_isr() can be static
Date: Fri, 8 Jun 2018 23:44:49 +0800 [thread overview]
Message-ID: <20180608154449.GA27070@xian> (raw)
In-Reply-To: <201806082323.j7tfjHHX%fengguang.wu@intel.com>
Fixes: 8079c81ec306 ("PCI/AER: Hoist aerdrv.c, aer_inject.c up to drivers/pci/pcie/")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
aer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c
index d84cc11..a2e8838 100644
--- a/drivers/pci/pcie/aer.c
+++ b/drivers/pci/pcie/aer.c
@@ -1035,7 +1035,7 @@ static int get_e_source(struct aer_rpc *rpc, struct aer_err_source *e_src)
*
* Invoked, as DPC, when root port records new detected error
*/
-void aer_isr(struct work_struct *work)
+static void aer_isr(struct work_struct *work)
{
struct aer_rpc *rpc = container_of(work, struct aer_rpc, dpc_handler);
struct aer_err_source uninitialized_var(e_src);
prev parent reply other threads:[~2018-06-08 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 15:44 [pci:pci/aer-squash 12/12] drivers/pci/pcie/aer.c:1038:6: sparse: symbol 'aer_isr' was not declared. Should it be static? kbuild test robot
2018-06-08 15:44 ` kbuild test robot [this message]
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=20180608154449.GA27070@xian \
--to=fengguang.wu@intel.com \
--cc=bhelgaas@google.com \
--cc=kbuild-all@01.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).