From: kernel test robot <lkp@intel.com>
To: Stephan Gerhold <stephan@gerhold.net>,
Jonathan Cameron <jic23@kernel.org>
Cc: kbuild-all@lists.01.org, "Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Robert Yang" <decatf@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
~postmarketos/upstreaming@lists.sr.ht
Subject: [RFC PATCH] iio: accel: kxcjk-1013: kx0231025_regs can be static
Date: Tue, 11 May 2021 21:14:22 +0800 [thread overview]
Message-ID: <20210511131422.GA31783@86ca4a2db576> (raw)
In-Reply-To: <20210511095409.9290-4-stephan@gerhold.net>
drivers/iio/accel/kxcjk-1013.c:224:30: warning: symbol 'kx0231025_regs' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
kxcjk-1013.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
index 5aa2a1cb2309d..1e5e241f2bcdf 100644
--- a/drivers/iio/accel/kxcjk-1013.c
+++ b/drivers/iio/accel/kxcjk-1013.c
@@ -221,7 +221,7 @@ const struct kx_chipset_regs kxtf9_regs = {
};
/* The registers have totally different names but the bits are compatible */
-const struct kx_chipset_regs kx0231025_regs = {
+static const struct kx_chipset_regs kx0231025_regs = {
.int_src1 = KX023_REG_INS2,
.int_src2 = KX023_REG_INS3,
.int_rel = KX023_REG_INT_REL,
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] iio: accel: kxcjk-1013: kx0231025_regs can be static
Date: Tue, 11 May 2021 21:14:22 +0800 [thread overview]
Message-ID: <20210511131422.GA31783@86ca4a2db576> (raw)
In-Reply-To: <20210511095409.9290-4-stephan@gerhold.net>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
drivers/iio/accel/kxcjk-1013.c:224:30: warning: symbol 'kx0231025_regs' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
kxcjk-1013.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
index 5aa2a1cb2309d..1e5e241f2bcdf 100644
--- a/drivers/iio/accel/kxcjk-1013.c
+++ b/drivers/iio/accel/kxcjk-1013.c
@@ -221,7 +221,7 @@ const struct kx_chipset_regs kxtf9_regs = {
};
/* The registers have totally different names but the bits are compatible */
-const struct kx_chipset_regs kx0231025_regs = {
+static const struct kx_chipset_regs kx0231025_regs = {
.int_src1 = KX023_REG_INS2,
.int_src2 = KX023_REG_INS3,
.int_rel = KX023_REG_INT_REL,
next prev parent reply other threads:[~2021-05-11 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 9:54 [PATCH 0/3] iio: accel: kxcjk-1013: Add support for KX023-1025 Stephan Gerhold
2021-05-11 9:54 ` [PATCH 1/3] dt-bindings: iio: kionix,kxcjk1013: Document kionix,kx023-1025 Stephan Gerhold
2021-05-11 9:54 ` [PATCH 2/3] iio: accel: kxcjk-1013: Refactor configuration registers into struct Stephan Gerhold
2021-05-11 12:37 ` kernel test robot
2021-05-11 12:37 ` kernel test robot
2021-05-11 12:37 ` [RFC PATCH] iio: accel: kxcjk-1013: kxcjk1013_regs can be static kernel test robot
2021-05-11 12:37 ` kernel test robot
2021-05-11 9:54 ` [PATCH 3/3] iio: accel: kxcjk-1013: Add support for KX023-1025 Stephan Gerhold
2021-05-11 13:14 ` kernel test robot
2021-05-11 13:14 ` kernel test robot
2021-05-11 13:14 ` kernel test robot [this message]
2021-05-11 13:14 ` [RFC PATCH] iio: accel: kxcjk-1013: kx0231025_regs can be static kernel test robot
2021-05-11 10:44 ` [PATCH 0/3] iio: accel: kxcjk-1013: Add support for KX023-1025 Hans de Goede
2021-05-11 14:10 ` Jonathan Cameron
2021-05-11 14:28 ` Michał Mirosław
2021-05-11 14:38 ` Stephan Gerhold
2021-05-11 14:50 ` Michał Mirosław
2021-05-13 16:14 ` Jonathan Cameron
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=20210511131422.GA31783@86ca4a2db576 \
--to=lkp@intel.com \
--cc=decatf@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=robh+dt@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.