From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v3 uq/master 00/22] Win32 iothread support Date: Mon, 28 Feb 2011 12:57:06 +0100 Message-ID: <4D6B8D92.8050807@siemens.com> References: <1298884224-19734-1-git-send-email-pbonzini@redhat.com> <4D6B67E0.4040408@redhat.com> <4D6B7479.5010307@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , qemu-devel@nongnu.org, kvm@vger.kernel.org, aurelien@aurel32.net, blauwirbel@gmail.com, mtosatti@redhat.com To: Paolo Bonzini Return-path: Received: from david.siemens.de ([192.35.17.14]:16778 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753280Ab1B1L5c (ORCPT ); Mon, 28 Feb 2011 06:57:32 -0500 In-Reply-To: <4D6B7479.5010307@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-02-28 11:10, Paolo Bonzini wrote: > On 02/28/2011 10:16 AM, Avi Kivity wrote: >> Why is that? uq/master is for kvm code, and this touches two or three >> lines? > > iothread code is also going in via uq/master often. I started with > uq/master because I depended on Jan's changes which are now upstream, I > have no problems with this going directly to qemu.git. As this touches the iothread, a central subsystem full of kvm code, and as uq/master is known to be checked against autotest, I still think uq/master is the right choice. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux