From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:59947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUsk5-0004kt-VZ for qemu-devel@nongnu.org; Wed, 24 Apr 2013 01:59:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUsk5-0005tE-4a for qemu-devel@nongnu.org; Wed, 24 Apr 2013 01:59:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:18442) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUsk4-0005t1-Te for qemu-devel@nongnu.org; Wed, 24 Apr 2013 01:59:45 -0400 Message-ID: <517774C8.2030604@redhat.com> Date: Wed, 24 Apr 2013 07:59:36 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <1366381460-6041-1-git-send-email-pbonzini@redhat.com> <1366759020.13769.49.camel@haakon3.risingtidesystems.com> In-Reply-To: <1366759020.13769.49.camel@haakon3.risingtidesystems.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] seabios for qemu 1.5 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Nicholas A. Bellinger" Cc: Kevin O'Connor , "Michael S. Tsirkin" , "seabios@seabios.org" , qemu-devel@nongnu.org, target-devel , Anthony Liguori , Paolo Bonzini , asias@redhat.com Hi, > b44a7be17bdd270ea029a8e2ec0c2e80c6cd0444 virtio-scsi: Pack struct virtio_scsi_{req_cmd,resp_cmd} > 5a7730db57ab0715223421e65b54fb50d6fefe5c virtio-scsi: Set _DRIVER_OK flag before scsi target scanning > Anthony + Gerd, can we expect an rev to pc-bios/bios.bin soon to pick up > these seabios changes for vhost-scsi..? I don't feel like placing a seabios git snapshot into qemu. I think we should just cherry-pick everything we need for qemu 1.5 into the 1.7.2-stable branch, roll out a 1.7.2.2 release and put that into qemu 1.5. So, what will be needed? (1) The two commits listed above. (2) The patch for the pvpanic device (assuming it gets merged for 1.5). Anything else? Hard freeze for qemu 1.5 is next Wednesday. cheers, Gerd PS: For qemu 1.6 (which will hopefully include the acpi table reorganization) we will need a new release from the master branch and thus a bit more careful release planning.