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: [RFC PATCH] ptp: clock_pair_gpa can be static
Date: Wed, 9 Dec 2020 18:23:22 +0800 [thread overview]
Message-ID: <20201209102322.GA48751@21f297abc363> (raw)
In-Reply-To: <20201209060932.212364-4-jianyong.wu@arm.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
ptp_kvm_x86.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ptp/ptp_kvm_x86.c b/drivers/ptp/ptp_kvm_x86.c
index e011d691e549a7..19cad4c0297265 100644
--- a/drivers/ptp/ptp_kvm_x86.c
+++ b/drivers/ptp/ptp_kvm_x86.c
@@ -15,8 +15,8 @@
#include <linux/ptp_clock_kernel.h>
#include <linux/ptp_kvm.h>
-phys_addr_t clock_pair_gpa;
-struct kvm_clock_pairing clock_pair;
+static phys_addr_t clock_pair_gpa;
+static struct kvm_clock_pairing clock_pair;
struct pvclock_vsyscall_time_info *hv_clock;
int kvm_arch_ptp_init(void)
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH] ptp: clock_pair_gpa can be static
Date: Wed, 09 Dec 2020 18:23:22 +0800 [thread overview]
Message-ID: <20201209102322.GA48751@21f297abc363> (raw)
In-Reply-To: <20201209060932.212364-4-jianyong.wu@arm.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
ptp_kvm_x86.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ptp/ptp_kvm_x86.c b/drivers/ptp/ptp_kvm_x86.c
index e011d691e549a7..19cad4c0297265 100644
--- a/drivers/ptp/ptp_kvm_x86.c
+++ b/drivers/ptp/ptp_kvm_x86.c
@@ -15,8 +15,8 @@
#include <linux/ptp_clock_kernel.h>
#include <linux/ptp_kvm.h>
-phys_addr_t clock_pair_gpa;
-struct kvm_clock_pairing clock_pair;
+static phys_addr_t clock_pair_gpa;
+static struct kvm_clock_pairing clock_pair;
struct pvclock_vsyscall_time_info *hv_clock;
int kvm_arch_ptp_init(void)
next prev parent reply other threads:[~2020-12-09 10:24 UTC|newest]
Thread overview: 61+ 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 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 1/9] arm64: Probe for the presence of KVM hypervisor Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2021-02-02 13:18 ` Marc Zyngier
2021-02-02 13:18 ` Marc Zyngier
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 ` Jianyong Wu
2020-12-09 6:09 ` 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 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 10:23 ` kernel test robot
2020-12-09 10:23 ` kernel test robot
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
2021-02-02 13:23 ` Marc Zyngier
2021-02-02 13:23 ` 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 ` Jianyong Wu
2020-12-09 6:09 ` 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 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` [PATCH v16 6/9] arm64/kvm: Add hypercall service for kvm ptp Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2021-02-02 13:32 ` Marc Zyngier
2021-02-02 13:32 ` Marc Zyngier
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
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2021-02-02 13:37 ` Marc Zyngier
2021-02-02 13:37 ` Marc Zyngier
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
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2021-02-02 13:43 ` Marc Zyngier
2021-02-02 13:43 ` Marc Zyngier
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
2020-12-09 6:09 ` Jianyong Wu
2020-12-09 6:09 ` Jianyong Wu
2021-02-02 13:44 ` Marc Zyngier
2021-02-02 13:44 ` Marc Zyngier
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-01-06 8:29 ` Jianyong Wu
2021-01-06 8:29 ` Jianyong Wu
2021-02-02 14:15 ` Marc Zyngier
2021-02-02 14:15 ` Marc Zyngier
2021-02-02 14:15 ` Marc Zyngier
2021-02-03 2:40 ` Jianyong Wu
2021-02-03 2:40 ` Jianyong Wu
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=20201209102322.GA48751@21f297abc363 \
--to=lkp@intel.com \
--cc=Mark.Rutland@arm.com \
--cc=jianyong.wu@arm.com \
--cc=john.stultz@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=maz@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=yangbo.lu@nxp.com \
/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.