From: kbuild test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH nomadik] iio: light: gp2ap002_illuminance_table[] can be static
Date: Sun, 29 Dec 2019 18:23:00 +0800 [thread overview]
Message-ID: <20191229102237.4bexrcuc5otlbafe@f53c9c00458a> (raw)
In-Reply-To: <201912291830.oupM1vWE%lkp@intel.com>
Fixes: f095962c5090 ("iio: light: Add a driver for Sharp GP2AP002x00F")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
gp2ap002.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/light/gp2ap002.c b/drivers/iio/light/gp2ap002.c
index 98553041d63cd..6964719d21222 100644
--- a/drivers/iio/light/gp2ap002.c
+++ b/drivers/iio/light/gp2ap002.c
@@ -193,7 +193,7 @@ struct gp2ap002_illuminance {
* This mapping is based on the following formula.
* illuminance = 10 ^ (current / 10)
*/
-const struct gp2ap002_illuminance gp2ap002_illuminance_table[] = {
+static const struct gp2ap002_illuminance gp2ap002_illuminance_table[] = {
{ .curr = 5, .lux = 3 },
{ .curr = 6, .lux = 4 },
{ .curr = 7, .lux = 5 },
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-29 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 10:19 [nomadik:ux500-skomer-v5.5-rc1 62/63] drivers/iio/light/gp2ap002.c:196:35: sparse: sparse: symbol 'gp2ap002_illuminance_table' was not declared. Should it be static? kbuild test robot
2019-12-29 10:23 ` 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=20191229102237.4bexrcuc5otlbafe@f53c9c00458a \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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