From: kernel test robot <lkp@intel.com>
To: Asmaa Mnebhi <asmaa@nvidia.com>,
andy.shevchenko@gmail.com, linux-gpio@vger.kernel.org,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
brgl@bgdev.pl, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Asmaa Mnebhi <asmaa@nvidia.com>
Subject: Re: [PATCH v2 2/2] gpio: mlxbf3: Support add_pin_ranges()
Date: Thu, 17 Aug 2023 19:00:01 +0800 [thread overview]
Message-ID: <202308171834.7ikT2B4p-lkp@intel.com> (raw)
In-Reply-To: <20230816154442.8417-3-asmaa@nvidia.com>
Hi Asmaa,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linusw-pinctrl/devel]
[also build test WARNING on linusw-pinctrl/for-next brgl/gpio/for-next linus/master v6.5-rc6 next-20230816]
[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/Asmaa-Mnebhi/pinctrl-mlxbf3-Remove-gpio_disable_free/20230816-234711
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
patch link: https://lore.kernel.org/r/20230816154442.8417-3-asmaa%40nvidia.com
patch subject: [PATCH v2 2/2] gpio: mlxbf3: Support add_pin_ranges()
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20230817/202308171834.7ikT2B4p-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230817/202308171834.7ikT2B4p-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/202308171834.7ikT2B4p-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpio/gpio-mlxbf3.c: In function 'mlxbf3_gpio_add_pin_ranges':
>> drivers/gpio/gpio-mlxbf3.c:164:13: warning: unused variable 'ret' [-Wunused-variable]
164 | int ret;
| ^~~
vim +/ret +164 drivers/gpio/gpio-mlxbf3.c
160
161 static int mlxbf3_gpio_add_pin_ranges(struct gpio_chip *chip)
162 {
163 unsigned int id = 0;
> 164 int ret;
165
166 if (chip->ngpio % MLXBF3_GPIO_MAX_PINS_PER_BLOCK)
167 id = 1;
168
169 return gpiochip_add_pin_range(chip, "MLNXBF34:00",
170 chip->base, id * MLXBF3_GPIO_MAX_PINS_PER_BLOCK,
171 chip->ngpio);
172 }
173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-08-17 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 15:44 [PATCH v2 0/2] Fix Nvidia BlueField-3 GPIO access Asmaa Mnebhi
2023-08-16 15:44 ` [PATCH v2 1/2] pinctrl: mlxbf3: Remove gpio_disable_free() Asmaa Mnebhi
2023-08-16 15:44 ` [PATCH v2 2/2] gpio: mlxbf3: Support add_pin_ranges() Asmaa Mnebhi
2023-08-16 15:49 ` Andy Shevchenko
2023-08-16 21:28 ` Asmaa Mnebhi
2023-08-17 8:21 ` Andy Shevchenko
2023-08-17 15:07 ` Asmaa Mnebhi
2023-08-17 1:55 ` kernel test robot
2023-08-17 11:00 ` 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=202308171834.7ikT2B4p-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=asmaa@nvidia.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.