From: kernel test robot <lkp@intel.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: kbuild-all@lists.01.org, "Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Fabiano Rosas" <farosas@linux.ibm.com>,
"David Stevens" <stevensd@chromium.org>,
"Cédric Le Goater" <clg@kaod.org>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH kernel v4] KVM: PPC: Merge powerpc's debugfs entry content into generic entry
Date: Wed, 29 Dec 2021 09:39:31 +0000 [thread overview]
Message-ID: <202112291710.E7bImDlB-lkp@intel.com> (raw)
In-Reply-To: <20211220012351.2719879-1-aik@ozlabs.ru>
Hi Alexey,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/topic/ppc-kvm]
[also build test ERROR on v5.16-rc7]
[cannot apply to next-20211224]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Alexey-Kardashevskiy/KVM-PPC-Merge-powerpc-s-debugfs-entry-content-into-generic-entry/20211220-092433
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git topic/ppc-kvm
config: powerpc64-randconfig-s031-20211228 (https://download.01.org/0day-ci/archive/20211229/202112291710.E7bImDlB-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/0day-ci/linux/commit/3d3a1a5e82517f5f1a5dd3d7131afb3aa4312d82
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Alexey-Kardashevskiy/KVM-PPC-Merge-powerpc-s-debugfs-entry-content-into-generic-entry/20211220-092433
git checkout 3d3a1a5e82517f5f1a5dd3d7131afb3aa4312d82
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=powerpc SHELL=/bin/bash arch/powerpc/kvm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> arch/powerpc/kvm/e500mc.c:384:32: error: initialization of 'int (*)(struct kvm_vcpu *, struct dentry *)' from incompatible pointer type 'void (*)(struct kvm_vcpu *, struct dentry *)' [-Werror=incompatible-pointer-types]
384 | .create_vcpu_debugfs = kvmppc_create_vcpu_debugfs_e500,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/powerpc/kvm/e500mc.c:384:32: note: (near initialization for 'kvm_ops_e500mc.create_vcpu_debugfs')
cc1: all warnings being treated as errors
vim +384 arch/powerpc/kvm/e500mc.c
369
370 static struct kvmppc_ops kvm_ops_e500mc = {
371 .get_sregs = kvmppc_core_get_sregs_e500mc,
372 .set_sregs = kvmppc_core_set_sregs_e500mc,
373 .get_one_reg = kvmppc_get_one_reg_e500mc,
374 .set_one_reg = kvmppc_set_one_reg_e500mc,
375 .vcpu_load = kvmppc_core_vcpu_load_e500mc,
376 .vcpu_put = kvmppc_core_vcpu_put_e500mc,
377 .vcpu_create = kvmppc_core_vcpu_create_e500mc,
378 .vcpu_free = kvmppc_core_vcpu_free_e500mc,
379 .init_vm = kvmppc_core_init_vm_e500mc,
380 .destroy_vm = kvmppc_core_destroy_vm_e500mc,
381 .emulate_op = kvmppc_core_emulate_op_e500,
382 .emulate_mtspr = kvmppc_core_emulate_mtspr_e500,
383 .emulate_mfspr = kvmppc_core_emulate_mfspr_e500,
> 384 .create_vcpu_debugfs = kvmppc_create_vcpu_debugfs_e500,
385 };
386
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
prev parent reply other threads:[~2021-12-29 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 1:23 [PATCH kernel v4] KVM: PPC: Merge powerpc's debugfs entry content into generic entry Alexey Kardashevskiy
2021-12-20 7:29 ` Cédric Le Goater
2021-12-21 5:38 ` Alexey Kardashevskiy
2021-12-21 8:22 ` Cédric Le Goater
2021-12-29 9:39 ` kernel test robot [this message]
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=202112291710.E7bImDlB-lkp@intel.com \
--to=lkp@intel.com \
--cc=aik@ozlabs.ru \
--cc=clg@kaod.org \
--cc=farosas@linux.ibm.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=stevensd@chromium.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).