From: kernel test robot <lkp@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: drivers/dma-buf/st-dma-fence-unwrap.c:125:13: warning: variable 'err' set but not used
Date: Wed, 25 May 2022 21:00:25 +0800 [thread overview]
Message-ID: <202205252017.OlDscDi2-lkp@intel.com> (raw)
Hi Christian,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fdaf9a5840acaab18694a19e0eb0aa51162eeeed
commit: 64a8f92fd783e750cdb81af75942dcd53bbf61bd dma-buf: add dma_fence_unwrap v2
date: 9 weeks ago
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20220525/202205252017.OlDscDi2-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64a8f92fd783e750cdb81af75942dcd53bbf61bd
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 64a8f92fd783e750cdb81af75942dcd53bbf61bd
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash drivers/dma-buf/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/dma-buf/st-dma-fence-unwrap.c: In function 'unwrap_array':
>> drivers/dma-buf/st-dma-fence-unwrap.c:125:13: warning: variable 'err' set but not used [-Wunused-but-set-variable]
125 | int err = 0;
| ^~~
drivers/dma-buf/st-dma-fence-unwrap.c: In function 'unwrap_chain':
drivers/dma-buf/st-dma-fence-unwrap.c:167:13: warning: variable 'err' set but not used [-Wunused-but-set-variable]
167 | int err = 0;
| ^~~
drivers/dma-buf/st-dma-fence-unwrap.c: In function 'unwrap_chain_array':
drivers/dma-buf/st-dma-fence-unwrap.c:209:13: warning: variable 'err' set but not used [-Wunused-but-set-variable]
209 | int err = 0;
| ^~~
vim +/err +125 drivers/dma-buf/st-dma-fence-unwrap.c
120
121 static int unwrap_array(void *arg)
122 {
123 struct dma_fence *fence, *f1, *f2, *array;
124 struct dma_fence_unwrap iter;
> 125 int err = 0;
126
127 f1 = mock_fence();
128 if (!f1)
129 return -ENOMEM;
130
131 f2 = mock_fence();
132 if (!f2) {
133 dma_fence_put(f1);
134 return -ENOMEM;
135 }
136
137 array = mock_array(2, f1, f2);
138 if (!array)
139 return -ENOMEM;
140
141 dma_fence_unwrap_for_each(fence, &iter, array) {
142 if (fence == f1) {
143 f1 = NULL;
144 } else if (fence == f2) {
145 f2 = NULL;
146 } else {
147 pr_err("Unexpected fence!\n");
148 err = -EINVAL;
149 }
150 }
151
152 if (f1 || f2) {
153 pr_err("Not all fences seen!\n");
154 err = -EINVAL;
155 }
156
157 dma_fence_signal(f1);
158 dma_fence_signal(f2);
159 dma_fence_put(array);
160 return 0;
161 }
162
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-25 13:01 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=202205252017.OlDscDi2-lkp@intel.com \
--to=lkp@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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.