From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 00 of 10] Qemu PowerPC fixes and enhancements Date: Sun, 04 May 2008 11:17:04 +0300 Message-ID: <481D7100.2030808@qumranet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net To: Hollis Blanchard Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Hollis Blanchard wrote: > Avi, please apply these patches to the kvm-userspace repository. I've submitted > the device emulation patches (UIC and PCI) to qemu-devel, but have received no > response. > > Applied all, thanks. > Thinking ahead to qemu integration, many of these should be folded into a > single "Bamboo board" patch, but e.g. the device emulation patches are > logically separate. Do you track qemu patches for upstream integration like > you do for the kernel? Do you want me to keep these split-out patches locally? > Unsplitting them later would be a pain... > It's better to keep the patches split. As you point out, folding patches together is easy but splitting them later is hard. I don't keep a qemu patch queue; whether to take patches from kvm-userspace.git or rediff against upstream qemu is a decision that is best taken on a case-by-case basis, if and when qemu upstream becomes receptive to these patches. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone