From: kbuild test robot <lkp@intel.com>
To: Wang Wenhu <wenhu.wang@vivo.com>,
gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
kernel@vivo.com, robh@kernel.org,
Christophe Leroy <christophe.leroy@c-s.fr>,
Scott Wood <oss@buserror.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Randy Dunlap <rdunlap@infradead.org>
Cc: robh@kernel.org, kbuild-all@lists.01.org,
Scott Wood <oss@buserror.net>,
kernel@vivo.com, Wang Wenhu <wenhu.wang@vivo.com>
Subject: Re: [PATCH v2] misc: new driver sram_uapi for user level SRAM access
Date: Mon, 4 May 2020 22:51:55 +0800 [thread overview]
Message-ID: <202005042233.TRh5ui7l%lkp@intel.com> (raw)
In-Reply-To: <20200419123011.86765-1-wenhu.wang@vivo.com>
[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]
Hi Wang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on arm-soc/for-next linus/master linux/master v5.7-rc3 next-20200501]
[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/Wang-Wenhu/misc-new-driver-sram_uapi-for-user-level-SRAM-access/20200421-105427
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git ae83d0b416db002fe95601e7f97f64b59514d936
config: microblaze-allyesconfig (attached as .config)
compiler: microblaze-linux-gcc (GCC) 9.3.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
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=microblaze
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/misc/sram_uapi.c: In function 'sram_uapi_ioctl':
>> drivers/misc/sram_uapi.c:100:6: warning: 'type' may be used uninitialized in this function [-Wmaybe-uninitialized]
100 | if (cur->type == type) {
| ^
drivers/misc/sram_uapi.c:188:8: note: 'type' was declared here
188 | __u32 type;
| ^~~~
vim +/type +100 drivers/misc/sram_uapi.c
93
94 static struct sram_api *get_sram_api_from_type(__u32 type)
95 {
96 struct sram_api *cur;
97
98 mutex_lock(&sram_list_lock);
99 list_for_each_entry(cur, &sram_list, list) {
> 100 if (cur->type == type) {
101 kref_get(&cur->kref);
102 mutex_unlock(&sram_list_lock);
103 return cur;
104 }
105 }
106 mutex_unlock(&sram_list_lock);
107
108 return NULL;
109 }
110
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 62734 bytes --]
prev parent reply other threads:[~2020-05-04 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 12:30 [PATCH v2] misc: new driver sram_uapi for user level SRAM access Wang Wenhu
2020-05-04 14:51 ` 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=202005042233.TRh5ui7l%lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=christophe.leroy@c-s.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=kernel@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=wenhu.wang@vivo.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;
as well as URLs for NNTP newsgroup(s).