From: kbuild test robot <lkp@intel.com>
To: Juergen Gross <jgross@suse.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, xen-devel@lists.xenproject.org
Subject: [tip:x86/paravirt 2/15] arch/x86/xen/mmu_pv.c:105:1: sparse: symbol 'xen_reservation_lock' was not declared. Should it be static?
Date: Tue, 4 Sep 2018 23:25:39 +0800 [thread overview]
Message-ID: <20180904152539.GW17047@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/paravirt
head: 495310e4f2dd857c4d5a62806a04cb8ba53855c1
commit: f030aade9165080f3539fb86fc2ce9ffc391813c [2/15] x86/xen: Move pv specific parts of arch/x86/xen/mmu.c to mmu_pv.c
reproduce:
# apt-get install sparse
git checkout f030aade9165080f3539fb86fc2ce9ffc391813c
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
:::::: branch date: 3 hours ago
:::::: commit date: 3 hours ago
>> arch/x86/xen/mmu_pv.c:105:1: sparse: symbol 'xen_reservation_lock' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:373:20: sparse: symbol 'xen_pte_val' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:381:20: sparse: symbol 'xen_pgd_val' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:387:17: sparse: symbol 'xen_make_pte' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:395:17: sparse: symbol 'xen_make_pgd' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:402:20: sparse: symbol 'xen_pmd_val' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:460:17: sparse: symbol 'xen_make_pmd' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:468:20: sparse: symbol 'xen_pud_val' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:474:17: sparse: symbol 'xen_make_pud' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:558:20: sparse: symbol 'xen_p4d_val' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:564:17: sparse: symbol 'xen_make_p4d' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:1547:17: sparse: symbol 'xen_make_pte_init' was not declared. Should it be static?
arch/x86/xen/mmu_pv.c:2101:45: sparse: expression using sizeof(void)
arch/x86/xen/mmu_pv.c:2105:51: sparse: expression using sizeof(void)
arch/x86/xen/mmu_pv.c:2110:59: sparse: expression using sizeof(void)
arch/x86/xen/mmu_pv.c:2748:29: sparse: expression using sizeof(void)
arch/x86/xen/mmu_pv.c:694:19: sparse: context imbalance in 'xen_pte_lock' - wrong count at exit
arch/x86/xen/mmu_pv.c:706:13: sparse: context imbalance in 'xen_pte_unlock' - unexpected unlock
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next reply other threads:[~2018-09-04 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 15:25 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-04 15:25 [tip:x86/paravirt 2/15] arch/x86/xen/mmu_pv.c:105:1: sparse: symbol 'xen_reservation_lock' was not declared. Should it be static? kbuild test robot
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=20180904152539.GW17047@intel.com \
--to=lkp@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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 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.