From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: Re: [PATCH] rtc: rv3028: Improve trickle charger logic
Date: Fri, 9 Jun 2023 04:57:34 +0800 [thread overview]
Message-ID: <202306090421.91eXRy6m-lkp@intel.com> (raw)
In-Reply-To: <20230608090446.2899646-1-andrej.picej@norik.com>
References: <20230608090446.2899646-1-andrej.picej@norik.com>
TO: Andrej Picej <andrej.picej@norik.com>
TO: a.zummo@towertech.it
TO: alexandre.belloni@bootlin.com
CC: linux-rtc@vger.kernel.org
CC: linux-kernel@vger.kernel.org
CC: upstream@phytec.de
Hi Andrej,
kernel test robot noticed the following build warnings:
[auto build test WARNING on abelloni/rtc-next]
[also build test WARNING on linus/master v6.4-rc5 next-20230608]
[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/Andrej-Picej/rtc-rv3028-Improve-trickle-charger-logic/20230608-190234
base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next
patch link: https://lore.kernel.org/r/20230608090446.2899646-1-andrej.picej%40norik.com
patch subject: [PATCH] rtc: rv3028: Improve trickle charger logic
config: x86_64-randconfig-a015-20230608 (https://download.01.org/0day-ci/archive/20230609/202306090421.91eXRy6m-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add abelloni https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git
git fetch abelloni rtc-next
git checkout abelloni/rtc-next
b4 shazam https://lore.kernel.org/r/20230608090446.2899646-1-andrej.picej@norik.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/
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/202306090421.91eXRy6m-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/rtc/rtc-rv3028.c:959:7: warning: variable 'val' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
if (i < ARRAY_SIZE(rv3028_trickle_resistors)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/rtc/rtc-rv3028.c:968:17: note: uninitialized use occurs here
if (val_old != val) {
^~~
drivers/rtc/rtc-rv3028.c:959:3: note: remove the 'if' if its condition is always true
if (i < ARRAY_SIZE(rv3028_trickle_resistors)) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/rtc/rtc-rv3028.c:863:18: note: initialize the variable 'val' to silence this warning
int val_old, val;
^
= 0
1 warning generated.
>> drivers/rtc/rtc-rv3028.o: warning: objtool: rv3028_probe() falls through to next function rv3028_nvram_read()
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-06-08 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 20:57 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-08 9:04 [PATCH] rtc: rv3028: Improve trickle charger logic Andrej Picej
2023-06-08 9:31 ` Alexandre Belloni
2023-06-08 10:35 ` Andrej Picej
2023-06-15 6:06 ` Andrej Picej
2023-06-08 14:48 ` 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=202306090421.91eXRy6m-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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.