From: kbuild test robot <fengguang.wu@intel.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH rcu] fixup! EXP iommu: stupid_workaround() can be static
Date: Sat, 9 Jun 2018 04:11:26 +0800 [thread overview]
Message-ID: <20180608201126.GA72227@cairo> (raw)
In-Reply-To: <201806090402.ONNRpjQE%fengguang.wu@intel.com>
Fixes: 814ee31d1f90 ("fixup! EXP iommu: Placeholder for fix in mainline")
Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
---
amd_iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index 46519d0..00dcafe 100644
--- a/drivers/iommu/amd_iommu.c
+++ b/drivers/iommu/amd_iommu.c
@@ -3563,7 +3563,7 @@ EXPORT_SYMBOL(amd_iommu_device_info);
static struct irq_chip amd_ir_chip;
static DEFINE_SPINLOCK(iommu_table_lock);
-void __maybe_unused stupid_workaround(void)
+static void __maybe_unused stupid_workaround(void)
{
spin_lock(&iommu_table_lock);
spin_unlock(&iommu_table_lock);
next prev parent reply other threads:[~2018-06-08 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 20:11 [rcu:rcu/dev 114/116] drivers/iommu/amd_iommu.c:3566:21: sparse: symbol 'stupid_workaround' was not declared. Should it be static? kbuild test robot
2018-06-08 20:11 ` kbuild test robot [this message]
2018-06-09 6:17 ` Paul E. McKenney
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=20180608201126.GA72227@cairo \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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 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.