From: kernel test robot <lkp@intel.com>
To: John Erasmus Mari Geronimo <johnerasmusmari.geronimo@analog.com>,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 1/3] hwmon: (max31827) refactor enum chips to chip info
Date: Thu, 9 Jan 2025 13:05:49 +0800 [thread overview]
Message-ID: <202501091228.9APcsnSs-lkp@intel.com> (raw)
In-Reply-To: <20250108082531.15467-2-johnerasmusmari.geronimo@analog.com>
Hi John,
kernel test robot noticed the following build warnings:
[auto build test WARNING on adc52dd4078067fabf1431036ba180eafd8a7eee]
url: https://github.com/intel-lab-lkp/linux/commits/John-Erasmus-Mari-Geronimo/hwmon-max31827-refactor-enum-chips-to-chip-info/20250108-162739
base: adc52dd4078067fabf1431036ba180eafd8a7eee
patch link: https://lore.kernel.org/r/20250108082531.15467-2-johnerasmusmari.geronimo%40analog.com
patch subject: [PATCH 1/3] hwmon: (max31827) refactor enum chips to chip info
config: hexagon-randconfig-001-20250109 (https://download.01.org/0day-ci/archive/20250109/202501091228.9APcsnSs-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250109/202501091228.9APcsnSs-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501091228.9APcsnSs-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/hwmon/max31827.c:93:40: warning: tentative definition of variable with internal linkage has incomplete non-array type 'const struct max31827_chip_info' [-Wtentative-definition-incomplete-type]
static const struct max31827_chip_info max31827;
^
drivers/hwmon/max31827.c:93:21: note: forward declaration of 'struct max31827_chip_info'
static const struct max31827_chip_info max31827;
^
drivers/hwmon/max31827.c:94:40: warning: tentative definition of variable with internal linkage has incomplete non-array type 'const struct max31827_chip_info' [-Wtentative-definition-incomplete-type]
static const struct max31827_chip_info max31828;
^
drivers/hwmon/max31827.c:93:21: note: forward declaration of 'struct max31827_chip_info'
static const struct max31827_chip_info max31827;
^
drivers/hwmon/max31827.c:95:40: warning: tentative definition of variable with internal linkage has incomplete non-array type 'const struct max31827_chip_info' [-Wtentative-definition-incomplete-type]
static const struct max31827_chip_info max31829;
^
drivers/hwmon/max31827.c:93:21: note: forward declaration of 'struct max31827_chip_info'
static const struct max31827_chip_info max31827;
^
drivers/hwmon/max31827.c:96:40: warning: tentative definition of variable with internal linkage has incomplete non-array type 'const struct max31827_chip_info' [-Wtentative-definition-incomplete-type]
static const struct max31827_chip_info max31875;
^
drivers/hwmon/max31827.c:93:21: note: forward declaration of 'struct max31827_chip_info'
static const struct max31827_chip_info max31827;
^
drivers/hwmon/max31827.c:602:1: error: expected expression
static const struct max31827_chip_info max31829 = {
^
drivers/hwmon/max31827.c:677:23: error: expected '}'
MODULE_LICENSE("GPL");
^
drivers/hwmon/max31827.c:598:51: note: to match this '{'
static const struct max31827_chip_info max31828 = {
^
drivers/hwmon/max31827.c:677:23: error: expected ';' after top level declarator
MODULE_LICENSE("GPL");
^
;
4 warnings and 3 errors generated.
vim +93 drivers/hwmon/max31827.c
91
92 struct max31827_state;
> 93 static const struct max31827_chip_info max31827;
94 static const struct max31827_chip_info max31828;
95 static const struct max31827_chip_info max31829;
96 static const struct max31827_chip_info max31875;
97
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-09 5:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 8:25 [PATCH 0/3] Add max31875 support John Erasmus Mari Geronimo
2025-01-08 8:25 ` [PATCH 1/3] hwmon: (max31827) refactor enum chips to chip info John Erasmus Mari Geronimo
2025-01-08 14:22 ` Guenter Roeck
2025-01-09 5:05 ` kernel test robot [this message]
2025-01-08 8:25 ` [PATCH 2/3] dt-bindings: hwmon: adi,max31827: add MAX31875 John Erasmus Mari Geronimo
2025-01-08 9:42 ` Krzysztof Kozlowski
2025-01-08 8:25 ` [PATCH 3/3] hwmon: (max31827) add max31875 support John Erasmus Mari Geronimo
2025-03-02 18:41 ` Guenter Roeck
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=202501091228.9APcsnSs-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=johnerasmusmari.geronimo@analog.com \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).