linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Václav Kubernát" <kubernat@cesnet.cz>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH linux-next] hwmon: fsp3y_info[] can be static
Date: Fri, 16 Apr 2021 21:50:22 +0800	[thread overview]
Message-ID: <20210416135022.GA45876@35342e253913> (raw)
In-Reply-To: <202104162123.Fg4Rp1u1-lkp@intel.com>


Fixes: fdf70b5de6f3 ("hwmon: Add driver for fsp-3y PSUs and PDUs")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 fsp-3y.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hwmon/pmbus/fsp-3y.c b/drivers/hwmon/pmbus/fsp-3y.c
index 3ff4bace9a85f..284b73aaed467 100644
--- a/drivers/hwmon/pmbus/fsp-3y.c
+++ b/drivers/hwmon/pmbus/fsp-3y.c
@@ -147,7 +147,7 @@ static int fsp3y_read_word_data(struct i2c_client *client, int page, int phase,
 	return i2c_smbus_read_word_data(client, reg);
 }
 
-struct pmbus_driver_info fsp3y_info[] = {
+static struct pmbus_driver_info fsp3y_info[] = {
 	[ym2151e] = {
 		.pages = 2,
 		.func[YM2151_PAGE_12V_LOG] =


      reply	other threads:[~2021-04-16 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 13:50 [linux-next:master 12235/13394] drivers/hwmon/pmbus/fsp-3y.c:150:26: sparse: sparse: symbol 'fsp3y_info' was not declared. Should it be static? kernel test robot
2021-04-16 13:50 ` kernel 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=20210416135022.GA45876@35342e253913 \
    --to=lkp@intel.com \
    --cc=jdelvare@suse.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kubernat@cesnet.cz \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    /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