From: kernel test robot <lkp@intel.com>
To: "Nuno Sá" <nuno.sa@analog.com>,
linux-input@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org
Cc: kbuild-all@lists.01.org, Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Michael Hennerich <michael.hennerich@analog.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH v3 01/10] input: keyboard: adp5588-keys: support gpi key events as 'gpio keys'
Date: Tue, 26 Jul 2022 18:30:40 +0800 [thread overview]
Message-ID: <202207261830.c3VuQ5P0-lkp@intel.com> (raw)
In-Reply-To: <20220721080423.156151-2-nuno.sa@analog.com>
Hi "Nuno,
I love your patch! Perhaps something to improve:
[auto build test WARNING on dtor-input/next]
[also build test WARNING on next-20220725]
[cannot apply to brgl/gpio/for-next hid/for-next linus/master v5.19-rc8]
[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/Nuno-S/adp5588-keys-refactor-and-fw-properties-support/20220721-160531
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config: x86_64-randconfig-a013 (https://download.01.org/0day-ci/archive/20220726/202207261830.c3VuQ5P0-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/357979f7c2525297178fb321c5793a4bd63dabb6
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nuno-S/adp5588-keys-refactor-and-fw-properties-support/20220721-160531
git checkout 357979f7c2525297178fb321c5793a4bd63dabb6
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/input/keyboard/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from include/linux/gpio/driver.h:6,
from drivers/input/keyboard/adp5588-keys.c:13:
drivers/input/keyboard/adp5588-keys.c: In function 'adp5588_gpiomap_get_hwirq':
>> include/linux/irq.h:1245:25: warning: overflow in conversion from 'long unsigned int' to 'int' changes value from '18446744073709551615' to '-1' [-Woverflow]
1245 | #define INVALID_HWIRQ (~0UL)
| ^
drivers/input/keyboard/adp5588-keys.c:336:16: note: in expansion of macro 'INVALID_HWIRQ'
336 | return INVALID_HWIRQ;
| ^~~~~~~~~~~~~
vim +1245 include/linux/irq.h
2f75d9e1c90511 Thomas Gleixner 2017-09-13 1243
d17bf24e695290 Qais Yousef 2015-12-08 1244 /* Contrary to Linux irqs, for hardware irqs the irq number 0 is valid */
d17bf24e695290 Qais Yousef 2015-12-08 @1245 #define INVALID_HWIRQ (~0UL)
f9bce791ae2a1a Qais Yousef 2015-12-08 1246 irq_hw_number_t ipi_get_hwirq(unsigned int irq, unsigned int cpu);
3b8e29a82dd16c Qais Yousef 2015-12-08 1247 int __ipi_send_single(struct irq_desc *desc, unsigned int cpu);
3b8e29a82dd16c Qais Yousef 2015-12-08 1248 int __ipi_send_mask(struct irq_desc *desc, const struct cpumask *dest);
3b8e29a82dd16c Qais Yousef 2015-12-08 1249 int ipi_send_single(unsigned int virq, unsigned int cpu);
3b8e29a82dd16c Qais Yousef 2015-12-08 1250 int ipi_send_mask(unsigned int virq, const struct cpumask *dest);
d17bf24e695290 Qais Yousef 2015-12-08 1251
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-26 10:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 8:04 [PATCH v3 00/10] adp5588-keys refactor and fw properties support Nuno Sá
2022-07-21 8:04 ` [PATCH v3 01/10] input: keyboard: adp5588-keys: support gpi key events as 'gpio keys' Nuno Sá
2022-07-23 4:56 ` kernel test robot
2022-07-25 20:31 ` Andy Shevchenko
2022-08-29 11:21 ` Sa, Nuno
2022-07-25 20:34 ` Andy Shevchenko
2022-08-29 11:20 ` Sa, Nuno
2022-07-26 10:30 ` kernel test robot [this message]
2022-08-31 12:24 ` Linus Walleij
2022-08-31 12:26 ` Andy Shevchenko
2022-08-31 12:28 ` Sa, Nuno
2022-08-31 12:30 ` Linus Walleij
2022-07-21 8:04 ` [PATCH v3 02/10] gpio: gpio-adp5588: drop the driver Nuno Sá
2022-07-21 8:04 ` [PATCH v3 03/10] input: keyboard: adp5588-keys: bail out on returned error Nuno Sá
2022-07-21 8:04 ` [PATCH v3 04/10] input: keyboard: adp5588-keys: add support for fw properties Nuno Sá
2022-07-21 8:04 ` [PATCH v3 05/10] dt-bindings: input: adp5588: add bindings Nuno Sá
2022-07-21 8:33 ` Krzysztof Kozlowski
2022-07-21 8:04 ` [PATCH v3 06/10] input: keyboard: adp5588-keys: do not check for irq presence Nuno Sá
2022-07-21 8:04 ` [PATCH v3 07/10] input: keyboard: adp5588-keys: fix coding style warnings Nuno Sá
2022-07-21 8:04 ` [PATCH v3 08/10] input: keyboard: adp5588-keys: add optional reset gpio Nuno Sá
2022-07-21 8:04 ` [PATCH v3 09/10] input: keyboard: adp5588-keys: add regulator support Nuno Sá
2022-07-21 8:04 ` [PATCH v3 10/10] input: keyboard: adp5588-keys: Use new PM macros Nuno Sá
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=202207261830.c3VuQ5P0-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--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;
as well as URLs for NNTP newsgroup(s).