From: Suzuki K Poulose <suzuki.poulose@arm.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.Deacon@arm.com
Cc: justin.he@arm.com, kvm@vger.kernel.org, Steve.Capper@arm.com,
linux-kernel@vger.kernel.org, Kaly.Xin@arm.com, nd@arm.com,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v4 2/5] ptp: Reorganize ptp_kvm modules to make it arch-independent.
Date: Fri, 27 Sep 2019 11:23:04 +0100 [thread overview]
Message-ID: <47ceb25c-c9ff-e284-43bf-6cac7e128a98@arm.com> (raw)
In-Reply-To: <20190926114212.5322-3-jianyong.wu@arm.com>
On 26/09/2019 12:42, Jianyong Wu wrote:
> Currently, ptp_kvm modules implementation is only for x86 which includs
> large part of arch-specific code. This patch move all of those code
> into new arch related file in the same directory.
>
> Signed-off-by: Jianyong Wu <jianyong.wu@arm.com>
...
> +int kvm_arch_ptp_get_clock_fn(unsigned long *cycle, struct timespec64 *tspec,
> + struct clocksource **cs)
> diff --git a/include/asm-generic/ptp_kvm.h b/include/asm-generic/ptp_kvm.h
> new file mode 100644
> index 000000000000..208e842bfa64
> --- /dev/null
> +++ b/include/asm-generic/ptp_kvm.h
> +int kvm_arch_ptp_get_clock_fn(long *cycle,
> + struct timespec64 *tspec, void *cs);
>
Conflicting types for kvm_arch_ptp_get_clock_fn() ?
Suzuki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-27 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 11:42 [RFC PATCH v4 0/6] Enable ptp_kvm for arm64 Jianyong Wu
2019-09-26 11:42 ` [RFC PATCH v4 1/5] psci: Export psci_ops.conduit symbol as modules will use it Jianyong Wu
2019-09-26 11:42 ` [RFC PATCH v4 2/5] ptp: Reorganize ptp_kvm modules to make it arch-independent Jianyong Wu
2019-09-26 13:06 ` Suzuki K Poulose
2019-09-27 10:10 ` Jianyong Wu (Arm Technology China)
2019-09-27 10:12 ` Suzuki K Poulose
2019-09-27 10:14 ` Jianyong Wu (Arm Technology China)
2019-09-27 10:23 ` Suzuki K Poulose [this message]
2019-09-27 10:35 ` Jianyong Wu (Arm Technology China)
2019-09-26 11:42 ` [RFC PATCH v4 3/5] psci: Add hvc call service for ptp_kvm Jianyong Wu
2019-09-27 9:20 ` Sergei Shtylyov
2019-09-26 11:42 ` [RFC PATCH v4 4/5] ptp: arm64: Enable ptp_kvm for arm64 Jianyong Wu
2019-09-26 11:42 ` [RFC PATCH v4 5/5] kvm: arm64: Add capability check extension for ptp_kvm 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=47ceb25c-c9ff-e284-43bf-6cac7e128a98@arm.com \
--to=suzuki.poulose@arm.com \
--cc=Kaly.Xin@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=Steve.Capper@arm.com \
--cc=Will.Deacon@arm.com \
--cc=jianyong.wu@arm.com \
--cc=john.stultz@linaro.org \
--cc=justin.he@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=richardcochran@gmail.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--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 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 NNTP newsgroup(s).