From: kbuild test robot <lkp@intel.com>
To: Jean-Jacques Hiblot <jjhiblot@ti.com>
Cc: kbuild-all@01.org, jacek.anaszewski@gmail.com, pavel@ucw.cz,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
dmurphy@ti.com, tomi.valkeinen@ti.com,
Jean-Jacques Hiblot <jjhiblot@ti.com>
Subject: Re: [PATCH v6 2/2] leds: Add control of the voltage/current regulator to the LED core
Date: Sat, 5 Oct 2019 10:32:29 +0800 [thread overview]
Message-ID: <201910051048.HyIbzklG%lkp@intel.com> (raw)
In-Reply-To: <20191004160724.18390-3-jjhiblot@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2337 bytes --]
Hi Jean-Jacques,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on j.anaszewski-leds/for-next]
[cannot apply to v5.4-rc1 next-20191004]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Jean-Jacques-Hiblot/leds-Add-control-of-the-voltage-current-regulator-to-the-LED-core/20191005-062631
base: https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
config: sparc-allyesconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/leds/led-core.c: In function 'try_turn_on_regulator_if_needed':
>> drivers/leds/led-core.c:65:15: warning: overflow in implicit constant conversion [-Woverflow]
atomic_and(~REG_R_ON, &led_cdev->regulator_state);
^
drivers/leds/led-core.c: In function 'led_set_brightness_nopm':
drivers/leds/led-core.c:353:27: warning: overflow in implicit constant conversion [-Woverflow]
old = atomic_fetch_and(~REG_U_ON,
^
vim +65 drivers/leds/led-core.c
54
55 static void try_turn_on_regulator_if_needed(struct led_classdev *led_cdev)
56 {
57 int old = atomic_cmpxchg(&led_cdev->regulator_state, REG_R_OFF_U_ON,
58 REG_R_ON_U_ON);
59 if (old == REG_R_OFF_U_ON) {
60 int rc = regulator_enable(led_cdev->regulator);
61
62 if (rc) {
63 dev_err(led_cdev->dev,
64 "Failed to enable the regulator (%d)\n", rc);
> 65 atomic_and(~REG_R_ON, &led_cdev->regulator_state);
66 }
67 }
68 }
69
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 59363 bytes --]
prev parent reply other threads:[~2019-10-05 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 16:07 [PATCH v6 0/2] " Jean-Jacques Hiblot
2019-10-04 16:07 ` [PATCH v6 1/2] dt-bindings: leds: document the "power-supply" property Jean-Jacques Hiblot
2019-10-04 16:07 ` [PATCH v6 2/2] leds: Add control of the voltage/current regulator to the LED core Jean-Jacques Hiblot
2019-10-05 2:32 ` kbuild 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=201910051048.HyIbzklG%lkp@intel.com \
--to=lkp@intel.com \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=jjhiblot@ti.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tomi.valkeinen@ti.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
all inboxes | Powered by JetHome®