From: kernel test robot <lkp@intel.com>
To: "Kyle Hsieh" <kylehsieh1995@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Beguin" <liambeguin@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Kyle Hsieh <kylehsieh1995@gmail.com>
Subject: Re: [PATCH 2/2] iio: adc: ltc2309: add support for ltc2305
Date: Wed, 24 Dec 2025 04:35:53 +0800 [thread overview]
Message-ID: <202512240416.ckqhNpHO-lkp@intel.com> (raw)
In-Reply-To: <20251223-add_ltc2305_driver-v1-2-dfa0827fd620@gmail.com>
Hi Kyle,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 9448598b22c50c8a5bb77a9103e2d49f134c9578]
url: https://github.com/intel-lab-lkp/linux/commits/Kyle-Hsieh/dt-bindings-adc-ltc2497-add-support-for-ltc2305/20251223-171509
base: 9448598b22c50c8a5bb77a9103e2d49f134c9578
patch link: https://lore.kernel.org/r/20251223-add_ltc2305_driver-v1-2-dfa0827fd620%40gmail.com
patch subject: [PATCH 2/2] iio: adc: ltc2309: add support for ltc2305
config: sparc64-randconfig-001-20251224 (https://download.01.org/0day-ci/archive/20251224/202512240416.ckqhNpHO-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512240416.ckqhNpHO-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/202512240416.ckqhNpHO-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/iio/adc/ltc2309.c: In function 'ltc2309_probe':
>> drivers/iio/adc/ltc2309.c:195:29: warning: unused variable 'match' [-Wunused-variable]
const struct of_device_id *match;
^~~~~
vim +/match +195 drivers/iio/adc/ltc2309.c
192
193 static int ltc2309_probe(struct i2c_client *client)
194 {
> 195 const struct of_device_id *match;
196 const struct ltc230x_chip_info *chip_info;
197 struct iio_dev *indio_dev;
198 struct ltc2309 *ltc2309;
199 int ret;
200
201 indio_dev = devm_iio_device_alloc(&client->dev, sizeof(*ltc2309));
202 if (!indio_dev)
203 return -ENOMEM;
204
205 ltc2309 = iio_priv(indio_dev);
206 chip_info = device_get_match_data(&client->dev);
207 if (!chip_info)
208 return -EINVAL;
209
210 ltc2309->dev = &indio_dev->dev;
211 ltc2309->client = client;
212
213 indio_dev->name = chip_info->name;
214 indio_dev->modes = INDIO_DIRECT_MODE;
215 indio_dev->channels = chip_info->channels;
216 indio_dev->num_channels = chip_info->num_channels;
217 indio_dev->info = <c2309_info;
218
219 ret = devm_regulator_get_enable_read_voltage(&client->dev, "vref");
220 if (ret < 0 && ret != -ENODEV)
221 return dev_err_probe(ltc2309->dev, ret,
222 "failed to get vref voltage\n");
223
224 ltc2309->vref_mv = ret == -ENODEV ? LTC2309_INTERNAL_REF_MV : ret / 1000;
225
226 mutex_init(<c2309->lock);
227
228 return devm_iio_device_register(&client->dev, indio_dev);
229 }
230
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-23 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 9:12 [PATCH 0/2] iio: adc: ltc2309: add support driver for ltc2305 Kyle Hsieh
2025-12-23 9:12 ` [PATCH 1/2] dt-bindings: adc: ltc2497: add support " Kyle Hsieh
2025-12-23 9:12 ` [PATCH 2/2] iio: adc: ltc2309: " Kyle Hsieh
2025-12-23 18:38 ` David Lechner
2025-12-24 5:06 ` Kyle Hsieh
2025-12-23 20:35 ` 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=202512240416.ckqhNpHO-lkp@intel.com \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=kylehsieh1995@gmail.com \
--cc=lars@metafoo.de \
--cc=liambeguin@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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