qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, rjones@redhat.com
Cc: mst@redhat.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	agraf@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Fix bugs in i6300esb watchdog timer
Date: Mon, 23 Mar 2015 09:12:00 +0100	[thread overview]
Message-ID: <550FCAD0.8080800@redhat.com> (raw)
In-Reply-To: <1427075508-12099-1-git-send-email-david@gibson.dropbear.id.au>



On 23/03/2015 02:51, David Gibson wrote:
> This series fixes two bugs in the i6300esb watchdog timer device.  The
> first only affects big-endian targets (including targets like ppc
> which support both endians, but are considered big-endian by default).
> The second affects all targets, but only when the guest uses unusually
> large timeout values.
> 
> Changes in v2:
>   * Use muldiv64() instead of an __int128_t
> 
> David Gibson (2):
>   i6300esb: Correct endiannness
>   i6300esb: Fix signed integer overflow
> 
>  hw/watchdog/wdt_i6300esb.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 

Thanks, queueing for 2.3.0-rc2.

Paolo

      parent reply	other threads:[~2015-03-23  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  1:51 [Qemu-devel] [PATCH v2 0/2] Fix bugs in i6300esb watchdog timer David Gibson
2015-03-23  1:51 ` [Qemu-devel] [PATCH v2 1/2] i6300esb: Correct endiannness David Gibson
2015-03-23  9:01   ` Richard W.M. Jones
2015-03-23  1:51 ` [Qemu-devel] [PATCH v2 2/2] i6300esb: Fix signed integer overflow David Gibson
2015-03-23  9:00   ` Richard W.M. Jones
2015-03-23  9:54   ` [Qemu-devel] [Qemu-ppc] " BALATON Zoltan
2015-03-24  0:22     ` David Gibson
2015-03-24  7:48       ` Paolo Bonzini
2015-03-23  8:12 ` Paolo Bonzini [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=550FCAD0.8080800@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rjones@redhat.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).