qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] ppc: do not use get_clock_realtime()
Date: Wed, 17 Dec 2014 13:00:59 +0100	[thread overview]
Message-ID: <5491707B.1010806@suse.de> (raw)
In-Reply-To: <1417010463-3527-1-git-send-email-pbonzini@redhat.com>



On 26.11.14 15:01, Paolo Bonzini wrote:
> Use the external qemu-timer API instead.
> 
> Cc: qemu-ppc@nongnu.org
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks, applied to ppc-next.


Alex

      parent reply	other threads:[~2014-12-17 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 14:01 [Qemu-devel] [PATCH] ppc: do not use get_clock_realtime() Paolo Bonzini
2014-11-27  0:51 ` Tony Breeds
2014-11-27 17:00   ` Paolo Bonzini
2014-12-05  6:14     ` Tony Breeds
2014-12-17 12:00 ` Alexander Graf [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=5491707B.1010806@suse.de \
    --to=agraf@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).