qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexey Korolev <alexey.korolev@endace.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Fix typo in i400FX chipset init code
Date: Wed, 21 Mar 2012 14:59:00 +0200	[thread overview]
Message-ID: <20120321125858.GA21467@redhat.com> (raw)
In-Reply-To: <1330479314.29508.7.camel@nzhmlwks0057.ad.endace.com>

On Wed, Feb 29, 2012 at 02:35:14PM +1300, Alexey Korolev wrote:
> Hi,
> 
> There is a typo in i440FX init code. This is causing problems when
> somebody wants to access 64bit PCI range.
> 
> 
> Signed-off-by: Alexey Korolev <alexey.korolev@endace.com>

I've fixed the commit message and applied.
How does one trigger the problem?
I'd like to know so I can test for it.

> ---
> 
>  hw/piix_pci.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/hw/piix_pci.c b/hw/piix_pci.c
> index 3ed3d90..aab8188 100644
> --- a/hw/piix_pci.c
> +++ b/hw/piix_pci.c
> @@ -353,7 +353,7 @@ PCIBus *i440fx_init(PCII440FXState **pi440fx_state, int *piix3_devfn,
>      b = i440fx_common_init("i440FX", pi440fx_state, piix3_devfn, isa_bus, pic,
>                             address_space_mem, address_space_io, ram_size,
>                             pci_hole_start, pci_hole_size,
> -                           pci_hole64_size, pci_hole64_size,
> +                           pci_hole64_start, pci_hole64_size,
>                             pci_memory, ram_memory);
>      return b;
>  }
> 
> 
> 
> 

  parent reply	other threads:[~2012-03-21 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  1:35 [Qemu-devel] [PATCH] Fix typo in i400FX chipset init code Alexey Korolev
2012-03-21  5:26 ` Alexey Korolev
2012-03-21 12:28   ` Markus Armbruster
2012-03-21 12:35     ` Andreas Färber
2012-03-21 12:32   ` Andreas Färber
2012-03-21 13:07     ` Michael S. Tsirkin
2012-03-21 12:59 ` Michael S. Tsirkin [this message]
2012-03-21 23:08   ` Alexey Korolev

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=20120321125858.GA21467@redhat.com \
    --to=mst@redhat.com \
    --cc=alexey.korolev@endace.com \
    --cc=qemu-devel@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).