From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: sound/soc/codecs/tlv320adc3xxx.c:845:55: warning: Boolean result is used in bitwise operation. Clarify expression with parentheses. [clarifyCondition]
Date: Wed, 26 Jan 2022 15:39:14 +0800 [thread overview]
Message-ID: <202201261506.aULQ6Ya2-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-kernel(a)vger.kernel.org
TO: Ricard Wanderlof <ricardw@axis.com>
CC: Mark Brown <broonie@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 0280e3c58f92b2fe0e8fbbdf8d386449168de4a8
commit: e9a3b57efd28fe889a98171bdc1e9e0dd7eb9a50 ASoC: codec: tlv320adc3xxx: New codec driver
date: 5 weeks ago
:::::: branch date: 13 hours ago
:::::: commit date: 5 weeks ago
compiler: nds32le-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> sound/soc/codecs/tlv320adc3xxx.c:845:55: warning: Boolean result is used in bitwise operation. Clarify expression with parentheses. [clarifyCondition]
ADC3XXX_GPIO_GPO << ADC3XXX_GPIO_CTRL_CFG_SHIFT |
^
vim +845 sound/soc/codecs/tlv320adc3xxx.c
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 834
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 835 static int adc3xxx_gpio_direction_out(struct gpio_chip *chip,
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 836 unsigned int offset, int value)
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 837 {
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 838 struct adc3xxx *adc3xxx = gpiochip_get_data(chip);
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 839
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 840 /* Set GPIO output function. */
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 841 return regmap_update_bits(adc3xxx->regmap,
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 842 adc3xxx_gpio_ctrl_reg[offset],
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 843 ADC3XXX_GPIO_CTRL_CFG_MASK |
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 844 ADC3XXX_GPIO_CTRL_OUTPUT_CTRL_MASK,
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 @845 ADC3XXX_GPIO_GPO << ADC3XXX_GPIO_CTRL_CFG_SHIFT |
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 846 !!value << ADC3XXX_GPIO_CTRL_OUTPUT_CTRL_SHIFT);
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 847 }
e9a3b57efd28fe8 Ricard Wanderlof 2021-12-15 848
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-01-26 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 7:39 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 19:49 sound/soc/codecs/tlv320adc3xxx.c:845:55: warning: Boolean result is used in bitwise operation. Clarify expression with parentheses. [clarifyCondition] kernel test robot
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=202201261506.aULQ6Ya2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.