From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [plbossart-sound:fix/regmap-gpios 21/23] drivers/gpio/gpio-regmap.c:36:15: warning: comparison is always false due to limited range of data type
Date: Fri, 29 May 2020 01:22:57 +0800 [thread overview]
Message-ID: <202005290155.cq19bM8y%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1577 bytes --]
tree: https://github.com/plbossart/sound fix/regmap-gpios
head: cba51e6099379d0d8b110c035e25736598a357dc
commit: 1b4257efce7e5ec1a01dffb723bbed65e26cc338 [21/23] transition to gpio_regmap
config: sparc64-randconfig-c021-20200528 (attached as .config)
compiler: sparc64-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
drivers/gpio/gpio-regmap.c: In function 'gpio_regmap_addr':
>> drivers/gpio/gpio-regmap.c:36:15: warning: comparison is always false due to limited range of data type [-Wtype-limits]
36 | return (addr == GPIO_REGMAP_ADDR_ZERO) ? 0 : addr;
| ^~
vim +36 drivers/gpio/gpio-regmap.c
176fcd6a2c030b Michael Walle 2020-05-25 33
176fcd6a2c030b Michael Walle 2020-05-25 34 static unsigned int gpio_regmap_addr(unsigned int addr)
176fcd6a2c030b Michael Walle 2020-05-25 35 {
176fcd6a2c030b Michael Walle 2020-05-25 @36 return (addr == GPIO_REGMAP_ADDR_ZERO) ? 0 : addr;
176fcd6a2c030b Michael Walle 2020-05-25 37 }
176fcd6a2c030b Michael Walle 2020-05-25 38
:::::: The code at line 36 was first introduced by commit
:::::: 176fcd6a2c030b65a0f99743fa8af2e2a7146788 gpio: add a reusable generic gpio_chip using regmap
:::::: TO: Michael Walle <michael@walle.cc>
:::::: CC: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31883 bytes --]
reply other threads:[~2020-05-28 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202005290155.cq19bM8y%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.