From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC v4 00/58] Memory API Date: Wed, 20 Jul 2011 13:43:51 +0200 Message-ID: <4E26BF77.7070705@siemens.com> References: <1310901265-32051-1-git-send-email-avi@redhat.com> <20110719135601.GA7194@redhat.com> <4E25B85C.1030809@siemens.com> <4E25BB7A.7030105@redhat.com> <4E25BF26.6080900@siemens.com> <4E268E20.5050807@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from david.siemens.de ([192.35.17.14]:19702 "EHLO david.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750980Ab1GTLn7 (ORCPT ); Wed, 20 Jul 2011 07:43:59 -0400 In-Reply-To: <4E268E20.5050807@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 2011-07-20 10:13, Avi Kivity wrote: > On 07/19/2011 08:30 PM, Jan Kiszka wrote: >>> Rebasing is already not so fun for me with 78 patches and counting. >>> Let's drop yours and focus of getting mine in shape, since it's a superset. >> >> The patches series are widely orthogonal except for both killing the >> obsolete start/stop logging logic. >> >> But I don't mind rebasing over yours - if something is finally merged at >> all. > > If you post patches I'll incorporate them in my patchset. They're > available in qemu-kvm.git branch memory-region. Is that branch up-to-date? It spits out tons of debug messages, making it unusable for any test. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40219) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjVC3-00052o-CP for qemu-devel@nongnu.org; Wed, 20 Jul 2011 07:44:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QjVC0-00089W-JF for qemu-devel@nongnu.org; Wed, 20 Jul 2011 07:43:58 -0400 Received: from david.siemens.de ([192.35.17.14]:27078) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QjVC0-00089D-0u for qemu-devel@nongnu.org; Wed, 20 Jul 2011 07:43:56 -0400 Message-ID: <4E26BF77.7070705@siemens.com> Date: Wed, 20 Jul 2011 13:43:51 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <1310901265-32051-1-git-send-email-avi@redhat.com> <20110719135601.GA7194@redhat.com> <4E25B85C.1030809@siemens.com> <4E25BB7A.7030105@redhat.com> <4E25BF26.6080900@siemens.com> <4E268E20.5050807@redhat.com> In-Reply-To: <4E268E20.5050807@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC v4 00/58] Memory API List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , "Michael S. Tsirkin" On 2011-07-20 10:13, Avi Kivity wrote: > On 07/19/2011 08:30 PM, Jan Kiszka wrote: >>> Rebasing is already not so fun for me with 78 patches and counting. >>> Let's drop yours and focus of getting mine in shape, since it's a superset. >> >> The patches series are widely orthogonal except for both killing the >> obsolete start/stop logging logic. >> >> But I don't mind rebasing over yours - if something is finally merged at >> all. > > If you post patches I'll incorporate them in my patchset. They're > available in qemu-kvm.git branch memory-region. Is that branch up-to-date? It spits out tons of debug messages, making it unusable for any test. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux