From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android13-5.15-2024-11 1/1] drivers/dma-buf/st-dma-fence-unwrap.c:125:13: warning: variable 'err' set but not used
Date: Sun, 03 May 2026 09:26:16 +0800 [thread overview]
Message-ID: <202605030934.HRBHsThu-lkp@intel.com> (raw)
Hi Christian,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android13-5.15-2024-11
head: bfd2ab010d7b36dd753731915553c4f37b98c6f6
commit: 169630111a051b0f07c69a71ca25895e0f4df83e [1/1] BACKPORT: dma-buf: add dma_fence_unwrap v2
config: arm-allyesconfig (https://download.01.org/0day-ci/archive/20260503/202605030934.HRBHsThu-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260503/202605030934.HRBHsThu-lkp@intel.com/reproduce)
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/202605030934.HRBHsThu-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://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-03 1:26 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=202605030934.HRBHsThu-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.