From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
James Morse <james.morse@arm.com>
Subject: arch/arm64/kvm/sys_regs.c:165 vcpu_write_sys_reg() warn: inconsistent indenting
Date: Sat, 13 Mar 2021 14:35:18 +0800 [thread overview]
Message-ID: <202103131411.SMDugXEO-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f296bfd5cd04cbb49b8fc9585adc280ab2b58624
commit: 7ea90bdd70c9cf82dfbaa54e7d9f296928679224 KVM: arm64: Refactor vcpu_{read,write}_sys_reg
date: 10 months ago
config: arm64-randconfig-m031-20210312 (attached as .config)
compiler: aarch64-linux-gcc (GCC) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
arch/arm64/kvm/sys_regs.c:165 vcpu_write_sys_reg() warn: inconsistent indenting
vim +165 arch/arm64/kvm/sys_regs.c
7ea90bdd70c9cf Marc Zyngier 2019-06-20 158
7ea90bdd70c9cf Marc Zyngier 2019-06-20 159 void vcpu_write_sys_reg(struct kvm_vcpu *vcpu, u64 val, int reg)
7ea90bdd70c9cf Marc Zyngier 2019-06-20 160 {
7ea90bdd70c9cf Marc Zyngier 2019-06-20 161 if (vcpu->arch.sysregs_loaded_on_cpu &&
7ea90bdd70c9cf Marc Zyngier 2019-06-20 162 __vcpu_write_sys_reg_to_cpu(val, reg))
7ea90bdd70c9cf Marc Zyngier 2019-06-20 163 return;
7ea90bdd70c9cf Marc Zyngier 2019-06-20 164
d47533dab9f50e Christoffer Dall 2017-12-23 @165 __vcpu_sys_reg(vcpu, reg) = val;
d47533dab9f50e Christoffer Dall 2017-12-23 166 }
d47533dab9f50e Christoffer Dall 2017-12-23 167
:::::: The code at line 165 was first introduced by commit
:::::: d47533dab9f50eeb7289a38035c39c9eadb1e048 KVM: arm64: Introduce framework for accessing deferred sysregs
:::::: TO: Christoffer Dall <christoffer.dall@linaro.org>
:::::: CC: Marc Zyngier <marc.zyngier@arm.com>
---
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: 29410 bytes --]
reply other threads:[~2021-03-13 6:36 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=202103131411.SMDugXEO-lkp@intel.com \
--to=lkp@intel.com \
--cc=james.morse@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox