From: Avi Kivity <avi@qumranet.com>
To: ehrhardt@linux.vnet.ibm.com
Cc: kvm@vger.kernel.org, hollisb@us.ibm.com, kvm-ppc@vger.kernel.org,
borntraeger@de.ibm.com
Subject: Re: [PATCH] kvmtrace: fix ktime_t type usage in kvm.h
Date: Tue, 15 Jul 2008 11:54:30 +0300 [thread overview]
Message-ID: <487C65C6.4050309@qumranet.com> (raw)
In-Reply-To: <1216110106-3961-1-git-send-email-ehrhardt@linux.vnet.ibm.com>
ehrhardt@linux.vnet.ibm.com wrote:
> From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
>
> This is a small but important change I unfortunately lost in one of my
> debugging patches which actually should only contain some printf's.
> This patch adds the ktime header since we now use ktime_t in this kvm.h.
> Even with all my tests I missed that, sorry for the inconvenience.
>
>
ktime_t is kernel internal anyway. I converted kvmtrace to use a u64
nsec timestamp.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2008-07-15 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 8:21 [PATCH] kvmtrace: fix ktime_t type usage in kvm.h ehrhardt
2008-07-15 8:54 ` Avi Kivity [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=487C65C6.4050309@qumranet.com \
--to=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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