From: kernel test robot <lkp@intel.com>
To: Iskren Chernev <iskren.chernev@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: kbuild-all@lists.01.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Iskren Chernev <iskren.chernev@gmail.com>
Subject: [RFC PATCH] power: supply: max17040: max17040_family[] can be static
Date: Tue, 9 Jun 2020 05:23:56 +0800 [thread overview]
Message-ID: <20200608212356.GA34456@af167214b55a> (raw)
In-Reply-To: <20200608182642.592848-2-iskren.chernev@gmail.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
max17040_battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/supply/max17040_battery.c b/drivers/power/supply/max17040_battery.c
index 4fd6cf7b60c71..78f04aba4f26a 100644
--- a/drivers/power/supply/max17040_battery.c
+++ b/drivers/power/supply/max17040_battery.c
@@ -62,7 +62,7 @@ struct chip_data {
u8 has_soc_alert;
};
-struct chip_data max17040_family[] = {
+static struct chip_data max17040_family[] = {
[ID_MAX17040] = {
.reset_val = 0x0054,
.vcell_shift = 4,
next prev parent reply other threads:[~2020-06-09 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 18:26 [PATCH 1/2] dt-bindints: power: supply: Document max17040 extensions Iskren Chernev
2020-06-08 18:26 ` [PATCH 2/2] power: supply: max17040: Support compatible devices Iskren Chernev
2020-06-08 21:23 ` kernel test robot
2020-06-08 21:23 ` kernel test robot [this message]
2020-06-08 22:20 ` kernel test robot
2020-06-17 20:51 ` [PATCH 1/2] dt-bindints: power: supply: Document max17040 extensions Rob Herring
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=20200608212356.GA34456@af167214b55a \
--to=lkp@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=iskren.chernev@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
--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).