From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:37064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rcupl-0004rz-Cr for qemu-devel@nongnu.org; Tue, 20 Dec 2011 03:14:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rcupk-0002E5-GM for qemu-devel@nongnu.org; Tue, 20 Dec 2011 03:14:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48266) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rcupk-0002Do-9p for qemu-devel@nongnu.org; Tue, 20 Dec 2011 03:14:00 -0500 Date: Tue, 20 Dec 2011 10:13:53 +0200 From: Gleb Natapov Message-ID: <20111220081353.GB26636@redhat.com> References: <4EECB1B0.7050404@codemonkey.ws> <4EECB3C5.6060608@codemonkey.ws> <20111217152514.GM2520@amd.home.annexia.org> <4EECC227.4060904@codemonkey.ws> <20111217164956.GA16848@morn.localdomain> <20111219103101.GB27938@redhat.com> <4EEF7595.7060301@codemonkey.ws> <20111219174307.GB2558@redhat.com> <4EEF7C53.6050800@codemonkey.ws> <20111220033802.GA24119@morn.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111220033802.GA24119@morn.localdomain> Subject: Re: [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: "seabios@seabios.org" , "Richard W.M. Jones" , qemu-devel@nongnu.org, Max Filippov , Avi Kivity , Amit Shah , Gerd Hoffmann On Mon, Dec 19, 2011 at 10:38:02PM -0500, Kevin O'Connor wrote: > On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote: > > We really need to update SeaBIOS whenever there is a bug that we > > know requires an update. Things breakdown because of one or more of > > the following reasons: > > > > 1) User submits a patch to seabios@, Kevin applies it. But that > > doesn't necessarily trigger anything happening in QEMU. > > > > Ideally, the above mentioned user would submit a submodule update once (1) happens. > > > > 2) Kevin fixes something on his own or someone else changes > > something in the broader SeaBIOS community. That may not even be > > visible in QEMU. > > There is another complexity here - it's not always clear to me when a > group pulls a particular revision of SeaBIOS. So, knowing who to > notify is harder. > Why not just pull recent Seabios into QEMU weekly (or as fast as Seabios HEAD moves). Before going into qemu rc stage ask Seabios for formal release. -- Gleb.