From: kernel test robot <lkp@intel.com>
To: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, arnd@arndb.de,
gregkh@linuxfoundation.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, abd.masalkhi@gmail.com
Subject: Re: [PATCH v3 2/3] misc: add driver for ST M24LR series RFID/NFC EEPROM chips
Date: Sat, 7 Jun 2025 19:33:20 +0800 [thread overview]
Message-ID: <202506071933.QIYSWX1a-lkp@intel.com> (raw)
In-Reply-To: <20250606120631.3140054-3-abd.masalkhi@gmail.com>
Hi Abd-Alrhman,
kernel test robot noticed the following build warnings:
[auto build test WARNING on char-misc/char-misc-linus]
[also build test WARNING on soc/for-next robh/for-next driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus v6.15]
[cannot apply to char-misc/char-misc-testing char-misc/char-misc-next linus/master next-20250606]
[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/Abd-Alrhman-Masalkhi/dt-bindings-eeprom-Add-ST-M24LR-support/20250606-201000
base: char-misc/char-misc-linus
patch link: https://lore.kernel.org/r/20250606120631.3140054-3-abd.masalkhi%40gmail.com
patch subject: [PATCH v3 2/3] misc: add driver for ST M24LR series RFID/NFC EEPROM chips
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20250607/202506071933.QIYSWX1a-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250607/202506071933.QIYSWX1a-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/202506071933.QIYSWX1a-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/misc/m24lr.c:341: warning: Function parameter or struct member 'is_eeprom' not described in 'm24lr_write'
vim +341 drivers/misc/m24lr.c
322
323 /**
324 * m24lr_write - write buffer to M24LR device with page alignment handling
325 * @m24lr: pointer to driver context
326 * @buf: data buffer to write
327 * @size: number of bytes to write
328 * @offset: target register address in the device
329 *
330 * Writes data to the M24LR device using regmap, split into chunks no larger
331 * than page_size to respect device-specific write limitations (e.g., page
332 * size or I2C hold-time concerns). Each chunk is aligned to the page boundary
333 * defined by page_size.
334 *
335 * Returns:
336 * Total number of bytes written on success,
337 * A negative error code if any write fails.
338 */
339 static ssize_t m24lr_write(struct m24lr *m24lr, const u8 *buf, size_t size,
340 unsigned int offset, bool is_eeprom)
> 341 {
342 unsigned int n, next_sector;
343 struct regmap *regmap;
344 ssize_t ret = 0;
345 long err;
346
347 if (is_eeprom)
348 regmap = m24lr->eeprom_regmap;
349 else
350 regmap = m24lr->ctl_regmap;
351
352 n = min(size, m24lr->page_size);
353 next_sector = roundup(offset + 1, m24lr->page_size);
354 if (offset + n > next_sector)
355 n = next_sector - offset;
356
357 mutex_lock(&m24lr->lock);
358 while (n) {
359 err = m24lr_regmap_write(regmap, buf, n, offset);
360 if (IS_ERR_VALUE(err)) {
361 mutex_unlock(&m24lr->lock);
362 if (ret)
363 return ret;
364 else
365 return err;
366 }
367
368 offset += n;
369 size -= n;
370 ret += n;
371 n = min(size, m24lr->page_size);
372 }
373 mutex_unlock(&m24lr->lock);
374
375 return ret;
376 }
377
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-07 11:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 12:06 [PATCH v3 0/3] Add support for STMicroelectronics M24LR EEPROM/NFC chips Abd-Alrhman Masalkhi
2025-06-06 12:06 ` [PATCH v3 1/3] dt-bindings: eeprom: Add ST M24LR support Abd-Alrhman Masalkhi
2025-06-06 13:10 ` Krzysztof Kozlowski
2025-06-06 15:06 ` Abd-Alrhman Masalkhi
2025-06-06 12:06 ` [PATCH v3 2/3] misc: add driver for ST M24LR series RFID/NFC EEPROM chips Abd-Alrhman Masalkhi
2025-06-06 12:19 ` Greg KH
2025-06-06 13:38 ` Abd-Alrhman Masalkhi
2025-06-06 12:25 ` Greg KH
2025-06-06 14:24 ` Abd-Alrhman Masalkhi
2025-06-06 15:58 ` Greg KH
2025-06-07 11:33 ` kernel test robot [this message]
2025-06-06 12:06 ` [PATCH v3 3/3] ABI: sysfs: add documentation for ST M24LR EEPROM and control interface Abd-Alrhman Masalkhi
2025-06-06 12:28 ` Greg KH
2025-06-06 14:46 ` Abd-Alrhman Masalkhi
2025-06-06 16:02 ` Greg KH
2025-06-07 9:18 ` [PATCH v3 1/3] dt-bindings: eeprom: Add ST M24LR support Abd-Alrhman Masalkhi
2025-06-07 9:25 ` [PATCH v3 3/3] ABI: sysfs: add documentation for ST M24LR EEPROM and control interface Abd-Alrhman Masalkhi
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=202506071933.QIYSWX1a-lkp@intel.com \
--to=lkp@intel.com \
--cc=abd.masalkhi@gmail.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®