From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57405) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SALGa-0005h3-F6 for qemu-devel@nongnu.org; Wed, 21 Mar 2012 09:08:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SALGY-0007EP-4C for qemu-devel@nongnu.org; Wed, 21 Mar 2012 09:07:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62522) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SALGX-0007E9-SQ for qemu-devel@nongnu.org; Wed, 21 Mar 2012 09:07:50 -0400 Date: Wed, 21 Mar 2012 15:07:19 +0200 From: "Michael S. Tsirkin" Message-ID: <20120321130717.GB21467@redhat.com> References: <1330479314.29508.7.camel@nzhmlwks0057.ad.endace.com> <1332307597.20383.2.camel@nzhmlwks0057.ad.endace.com> <4F69CA6C.8070203@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <4F69CA6C.8070203@suse.de> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] Fix typo in i400FX chipset init code List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andreas =?iso-8859-1?Q?F=E4rber?= Cc: alexey.korolev@endace.com, "qemu-devel@nongnu.org" On Wed, Mar 21, 2012 at 01:32:44PM +0100, Andreas F=E4rber wrote: > Hi, >=20 > Am 21.03.2012 06:26, schrieb Alexey Korolev: > >> 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 > >> --- > >> > >> 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_sta= te, int *piix3_devfn, > >> b =3D 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; > >> } > >> > >> > >> > > Hi there, > >=20 > > Any chance that someone could have a look and commit this? >=20 > A patch should never start with "Hi,", it should have a commit message > that can be applied unmodified to git, describing what area it touches, > what it changes and why. So, the the subject should start with, e.g., > "i440fx: Fix start of 64-bit hole" and go on to explain where exactly > that is and what it affects (does this resolve some guest-visible bug? > when was it introduced? i.e., does it need to be backported?). Repeatin= g > "typo" again and again is not helpful to understand the impact of a > commit when bisecting later on without seeing the code. >=20 > You forgot to cc the PCI maintainer. >=20 > Andreas Yes I'd like to see an explanation on how to trigger a bug too. OTOH the fix is clearly right, and it's not submitter's work to dig through history to find where was the bug added, that is too much to ask IMO. > --=20 > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrn= berg