From: kernel test robot <lkp@intel•com>
To: Jianyong Wu <jianyong.wu@arm•com>,
netdev@vger•kernel.org, yangbo.lu@nxp•com,
john.stultz@linaro•org, tglx@linutronix•de, pbonzini@redhat•com,
sean.j.christopherson@intel•com, maz@kernel•org,
richardcochran@gmail•com, Mark.Rutland@arm•com, will@kernel•org
Cc: kbuild-all@lists•01.org
Subject: Re: [PATCH v16 3/9] ptp: Reorganize ptp_kvm module to make it arch-independent.
Date: Wed, 9 Dec 2020 18:23:21 +0800 [thread overview]
Message-ID: <202012091823.mlVUUlIH-lkp@intel.com> (raw)
In-Reply-To: <20201209060932.212364-4-jianyong.wu@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
Hi Jianyong,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on kvmarm/next]
[also build test WARNING on linus/master v5.10-rc7 next-20201208]
[cannot apply to tip/timers/core kvm/linux-next]
[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/Jianyong-Wu/Enable-ptp_kvm-for-arm-arm64/20201209-141506
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git next
config: i386-randconfig-s001-20201209 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-179-ga00755aa-dirty
# https://github.com/0day-ci/linux/commit/35c13e9c526d0900f8d80f4b3f6a34234d29a911
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Jianyong-Wu/Enable-ptp_kvm-for-arm-arm64/20201209-141506
git checkout 35c13e9c526d0900f8d80f4b3f6a34234d29a911
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel•com>
"sparse warnings: (new ones prefixed by >>)"
>> drivers/ptp/ptp_kvm_x86.c:18:13: sparse: sparse: symbol 'clock_pair_gpa' was not declared. Should it be static?
>> drivers/ptp/ptp_kvm_x86.c:19:26: sparse: sparse: symbol 'clock_pair' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 30832 bytes --]
next prev parent reply other threads:[~2020-12-09 10:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 6:09 [PATCH v16 0/9] Enable ptp_kvm for arm/arm64 Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 1/9] arm64: Probe for the presence of KVM hypervisor Jianyong Wu
2021-02-02 13:18 ` Marc Zyngier
2020-12-09 6:09 ` [PATCH v16 2/9] arm/arm64: KVM: Advertise KVM UID to guests via SMCCC Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 3/9] ptp: Reorganize ptp_kvm module to make it arch-independent Jianyong Wu
2020-12-09 10:23 ` kernel test robot [this message]
2020-12-09 10:23 ` [RFC PATCH] ptp: clock_pair_gpa can be static kernel test robot
2021-02-02 13:23 ` [PATCH v16 3/9] ptp: Reorganize ptp_kvm module to make it arch-independent Marc Zyngier
2020-12-09 6:09 ` [PATCH v16 4/9] time: Add mechanism to recognize clocksource in time_get_snapshot Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 5/9] clocksource: Add clocksource id for arm arch counter Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 6/9] arm64/kvm: Add hypercall service for kvm ptp Jianyong Wu
2021-02-02 13:32 ` Marc Zyngier
2020-12-09 6:09 ` [PATCH v16 7/9] ptp: arm/arm64: Enable ptp_kvm for arm/arm64 Jianyong Wu
2021-02-02 13:37 ` Marc Zyngier
2020-12-09 6:09 ` [PATCH v16 8/9] doc: add ptp_kvm introduction for arm64 support Jianyong Wu
2021-02-02 13:43 ` Marc Zyngier
2020-12-09 6:09 ` [PATCH v16 9/9] arm64: Add kvm capability check extension for ptp_kvm Jianyong Wu
2021-02-02 13:44 ` Marc Zyngier
2021-01-06 8:29 ` [PATCH v16 0/9] Enable ptp_kvm for arm/arm64 Jianyong Wu
2021-02-02 14:15 ` Marc Zyngier
2021-02-03 2:40 ` Jianyong Wu
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=202012091823.mlVUUlIH-lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=Mark.Rutland@arm$(echo .)com \
--cc=jianyong.wu@arm$(echo .)com \
--cc=john.stultz@linaro$(echo .)org \
--cc=kbuild-all@lists$(echo .)01.org \
--cc=maz@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pbonzini@redhat$(echo .)com \
--cc=richardcochran@gmail$(echo .)com \
--cc=sean.j.christopherson@intel$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=will@kernel$(echo .)org \
--cc=yangbo.lu@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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