From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGGlP-0004pw-3g for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:18:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGGlI-0004o4-Cb for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:18:34 -0400 Received: from [199.232.76.173] (port=39990 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGGlI-0004nw-3y for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:18:28 -0400 Received: from mx2.redhat.com ([66.187.237.31]:33411) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGGlH-0000UT-GN for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:18:28 -0400 Date: Mon, 15 Jun 2009 21:16:22 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] Register uhci_reset() callback. Message-ID: <20090615181622.GA782@redhat.com> References: <20090611084808.GA19508@redhat.com> <4A3674F5.5080403@redhat.com> <20090615170201.GA3964@redhat.com> <200906151856.28009.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200906151856.28009.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org, Avi Kivity On Mon, Jun 15, 2009 at 06:56:26PM +0100, Paul Brook wrote: > > May be, but in this case after previous patch to reset interrupt level > > for each device at PCI bridge level was rejected on the premise that > > device should lower its own irq line on reset and since patches started > > flowing in to do just that, I did not expect that eloquent explanation > > would be needed for such trivial and obviously correct change. > > This argument makes no sense. The fact that you'd recently submitted very > similar looking patches which either got rejected or need modification is a > good argument for providing an explanation. How else are we supposed to know > that you're not just making the same mistake again? They was not even "similar looking". Have you followed the discussion that those patches generated? Look at this commit and especially its commit message: 32c86e95b. This commit is a direct result of the discussion previous patches generated. Look at my patch now. Looks similar, no? So people with commit permissions can follow lower standards that we mere mortals? -- Gleb.