From: kernel test robot <lkp@intel.com>
To: Ivan Mikhaylov <fr0st61te@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Ivan Mikhaylov <fr0st61te@gmail.com>
Subject: Re: [PATCH v2 2/2] iio: adc: Add driver support for MAX34408/9
Date: Sat, 30 Sep 2023 08:37:40 +0800 [thread overview]
Message-ID: <202309300847.Vb7WCpaN-lkp@intel.com> (raw)
In-Reply-To: <20230929200844.23316-3-fr0st61te@gmail.com>
Hi Ivan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on jic23-iio/togreg]
[also build test WARNING on robh/for-next linus/master v6.6-rc3 next-20230929]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ivan-Mikhaylov/dt-bindings-adc-provide-max34408-9-device-tree-binding-document/20230930-043842
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
patch link: https://lore.kernel.org/r/20230929200844.23316-3-fr0st61te%40gmail.com
patch subject: [PATCH v2 2/2] iio: adc: Add driver support for MAX34408/9
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230930/202309300847.Vb7WCpaN-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230930/202309300847.Vb7WCpaN-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/202309300847.Vb7WCpaN-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iio/adc/max34408.c:79: warning: Function parameter or member 'input1_rsense' not described in 'max34408_data'
>> drivers/iio/adc/max34408.c:79: warning: Function parameter or member 'input2_rsense' not described in 'max34408_data'
>> drivers/iio/adc/max34408.c:79: warning: Function parameter or member 'input3_rsense' not described in 'max34408_data'
>> drivers/iio/adc/max34408.c:79: warning: Function parameter or member 'input4_rsense' not described in 'max34408_data'
vim +79 drivers/iio/adc/max34408.c
62
63 /**
64 * struct max34408_data - max34408/max34409 specific data.
65 * @regmap: device register map.
66 * @dev: max34408 device.
67 * @lock: lock for protecting access to device hardware registers, mostly
68 * for read modify write cycles for control registers.
69 * @rsense: Rsense value in uOhm.
70 */
71 struct max34408_data {
72 struct regmap *regmap;
73 struct device *dev;
74 struct mutex lock;
75 u32 input1_rsense;
76 u32 input2_rsense;
77 u32 input3_rsense;
78 u32 input4_rsense;
> 79 };
80
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-30 0:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 20:08 [PATCH v2 0/2] Add maxim max34408/34409 ADC driver and yaml Ivan Mikhaylov
2023-09-29 20:08 ` [PATCH v2 1/2] dt-bindings: adc: provide max34408/9 device tree binding document Ivan Mikhaylov
2023-09-29 21:36 ` Rob Herring
2023-09-30 9:37 ` Conor Dooley
2023-09-30 14:09 ` Jonathan Cameron
2023-09-30 19:38 ` Ivan Mikhaylov
2023-10-02 9:21 ` Jonathan Cameron
2023-09-29 20:08 ` [PATCH v2 2/2] iio: adc: Add driver support for MAX34408/9 Ivan Mikhaylov
2023-09-30 0:37 ` kernel test robot [this message]
2023-09-30 14:23 ` 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=202309300847.Vb7WCpaN-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fr0st61te@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh+dt@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