From: kernel test robot <lkp@intel.com>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-s390@vger.kernel.org
Subject: [kvms390:sae 53/55] arch/s390/kvm/arm64/arm.c:232:13: warning: variable 'ret' set but not used
Date: Fri, 08 May 2026 21:22:44 +0800 [thread overview]
Message-ID: <202605082137.4rqrVNVY-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git sae
head: 23885833f845ad11c99c4f458692250fc75908c5
commit: f41388cd69dc147f0e8f0aeeebc40eb8d19b6745 [53/55] KVM; s390: arm64: Implement sysreg handling
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20260508/202605082137.4rqrVNVY-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260508/202605082137.4rqrVNVY-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/202605082137.4rqrVNVY-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/s390/kvm/arm64/arm.c: In function 'kvm_arch_vcpu_run_pid_change':
>> arch/s390/kvm/arm64/arm.c:232:13: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
232 | int ret;
| ^~~
vim +/ret +232 arch/s390/kvm/arm64/arm.c
228
229 int kvm_arch_vcpu_run_pid_change(struct kvm_vcpu *vcpu)
230 {
231 struct kvm *kvm = vcpu->kvm;
> 232 int ret;
233
234 if (!kvm_vcpu_initialized(vcpu))
235 return -ENOEXEC;
236
237 if (!kvm_arm_vcpu_is_finalized(vcpu))
238 return -EPERM;
239
240 if (likely(READ_ONCE(vcpu->pid)))
241 return 0;
242
243 ret = kvm_finalize_sys_regs(vcpu);
244
245 mutex_lock(&kvm->arch.config_lock);
246 set_bit(KVM_ARCH_FLAG_HAS_RAN_ONCE, &kvm->arch.flags);
247 mutex_unlock(&kvm->arch.config_lock);
248
249 return 0;
250 }
251
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-08 13:23 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=202605082137.4rqrVNVY-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-s390@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seiden@linux.ibm.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