From: kernel test robot <lkp@intel.com>
To: Thomas Richard <thomas.richard@bootlin.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v2 1/6] gpiolib: add gpiochip_add_pin_range_sparse() function
Date: Tue, 18 Mar 2025 14:00:08 +0800 [thread overview]
Message-ID: <202503181221.ubMklVAA-lkp@intel.com> (raw)
In-Reply-To: <20250317-aaeon-up-board-pinctrl-support-v2-1-36126e30aa62@bootlin.com>
Hi Thomas,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on 12b58398bffc23db89e715414399b0533255da51]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Richard/gpiolib-add-gpiochip_add_pin_range_sparse-function/20250317-234321
base: 12b58398bffc23db89e715414399b0533255da51
patch link: https://lore.kernel.org/r/20250317-aaeon-up-board-pinctrl-support-v2-1-36126e30aa62%40bootlin.com
patch subject: [PATCH RFC v2 1/6] gpiolib: add gpiochip_add_pin_range_sparse() function
config: i386-buildonly-randconfig-006-20250318 (https://download.01.org/0day-ci/archive/20250318/202503181221.ubMklVAA-lkp@intel.com/config)
compiler: clang version 20.1.0 (https://github.com/llvm/llvm-project 24a30daaa559829ad079f2ff7f73eb4e18095f88)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250318/202503181221.ubMklVAA-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/202503181221.ubMklVAA-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpio/gpiolib.c:2320: warning: Function parameter or struct member 'pins' not described in 'gpiochip_add_pin_range_sparse'
>> drivers/gpio/gpiolib.c:2320: warning: Excess function parameter 'pin_list' description in 'gpiochip_add_pin_range_sparse'
vim +2320 drivers/gpio/gpiolib.c
2300
2301 /**
2302 * gpiochip_add_pin_range_sparse() - add a range for GPIO <-> pin mapping
2303 * @gc: the gpiochip to add the range for
2304 * @pinctl_name: the dev_name() of the pin controller to map to
2305 * @gpio_offset: the start offset in the current gpio_chip number space
2306 * @pin_list: the list of pins to accumulate in this range
2307 * @npins: the number of pins to accumulate in this range
2308 *
2309 * Calling this function directly from a DeviceTree-supported
2310 * pinctrl driver is DEPRECATED. Please see Section 2.1 of
2311 * Documentation/devicetree/bindings/gpio/gpio.txt on how to
2312 * bind pinctrl and gpio drivers via the "gpio-ranges" property.
2313 *
2314 * Returns:
2315 * 0 on success, or a negative errno on failure.
2316 */
2317 int gpiochip_add_pin_range_sparse(struct gpio_chip *gc, const char *pinctl_name,
2318 unsigned int gpio_offset, unsigned int const *pins,
2319 unsigned int npins)
> 2320 {
2321 return __gpiochip_add_pin_range(gc, pinctl_name, gpio_offset, 0, pins,
2322 npins);
2323 }
2324 EXPORT_SYMBOL_GPL(gpiochip_add_pin_range_sparse);
2325
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-03-18 6:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250317-aaeon-up-board-pinctrl-support-v2-1-36126e30aa62@bootlin.com>]
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=202503181221.ubMklVAA-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.richard@bootlin.com \
/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