public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/arm64/kvm/hyp/nvhe/../exception.c:36 __vcpu_write_sys_reg() warn: inconsistent indenting
Date: Sun, 14 Mar 2021 03:00:02 +0800	[thread overview]
Message-ID: <202103140300.VlCSIvlc-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   f296bfd5cd04cbb49b8fc9585adc280ab2b58624
commit: bb666c472ca25efb38d1163131cc01546b3a653a KVM: arm64: Inject AArch64 exceptions from HYP
date:   4 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/hyp/nvhe/../exception.c:36 __vcpu_write_sys_reg() warn: inconsistent indenting
arch/arm64/kvm/hyp/vhe/../exception.c:36 __vcpu_write_sys_reg() warn: inconsistent indenting

vim +36 arch/arm64/kvm/hyp/nvhe/../exception.c

    30	
    31	static inline void __vcpu_write_sys_reg(struct kvm_vcpu *vcpu, u64 val, int reg)
    32	{
    33		if (__vcpu_write_sys_reg_to_cpu(val, reg))
    34			return;
    35	
  > 36		 __vcpu_sys_reg(vcpu, reg) = val;
    37	}
    38	

---
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: 30639 bytes --]

                 reply	other threads:[~2021-03-13 19: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=202103140300.VlCSIvlc-lkp@intel.com \
    --to=lkp@intel.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