devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: kxcjk1013_regs can be static
Date: Tue, 11 May 2021 20:37:58 +0800	[thread overview]
Message-ID: <20210511123758.GA70037@86ca4a2db576> (raw)
In-Reply-To: <20210511095409.9290-3-stephan@gerhold.net>

drivers/iio/accel/kxcjk-1013.c:150:30: warning: symbol 'kxcjk1013_regs' was not declared. Should it be static?
drivers/iio/accel/kxcjk-1013.c:162:30: warning: symbol 'kxtf9_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 |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
index 8800ebf47b5a7..492f576f97348 100644
--- a/drivers/iio/accel/kxcjk-1013.c
+++ b/drivers/iio/accel/kxcjk-1013.c
@@ -147,7 +147,7 @@ struct kx_chipset_regs {
 	u8 wake_thres;
 };
 
-const struct kx_chipset_regs kxcjk1013_regs = {
+static const struct kx_chipset_regs kxcjk1013_regs = {
 	.int_src1	= KXCJK1013_REG_INT_SRC1,
 	.int_src2	= KXCJK1013_REG_INT_SRC2,
 	.int_rel	= KXCJK1013_REG_INT_REL,
@@ -159,7 +159,7 @@ const struct kx_chipset_regs kxcjk1013_regs = {
 	.wake_thres	= KXCJK1013_REG_WAKE_THRES,
 };
 
-const struct kx_chipset_regs kxtf9_regs = {
+static const struct kx_chipset_regs kxtf9_regs = {
 	/* .int_src1 was moved to INT_SRC2 on KXTF9 */
 	.int_src1	= KXTF9_REG_INT_SRC2,
 	/* .int_src2 is not available */

  parent reply	other threads:[~2021-05-11 12:38 UTC|newest]

Thread overview: 14+ 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 [this message]
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   ` [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=20210511123758.GA70037@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 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).