From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34180) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbCDA-00030E-Dr for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:23:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RbCD9-00084o-6r for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:23:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:30015) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RbCD8-00084h-Ou for qemu-devel@nongnu.org; Thu, 15 Dec 2011 09:23:03 -0500 Message-ID: <4EEA02C2.1060400@redhat.com> Date: Thu, 15 Dec 2011 16:22:58 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1323956131-471-1-git-send-email-avi@redhat.com> <4EEA0258.7090708@redhat.com> In-Reply-To: <4EEA0258.7090708@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org On 12/15/2011 04:21 PM, Paolo Bonzini wrote: > >> cpu-common.h | 36 ----------------------------- >> exec-obsolete.h | 66 >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> exec.c | 3 ++ >> hw/etraxfs_eth.c | 3 -- >> memory.c | 3 ++ >> 5 files changed, 72 insertions(+), 39 deletions(-) >> create mode 100644 exec-obsolete.h > > > I would prefer exec-private.h or memory-private.h. Right now, the > situation is that exec.c provides a low-level interface to memory.c. > If the situation changes, the header will disappear. Since the header is going to disappear, does it really matter? I plan on removing it long before 1.1. -- error compiling committee.c: too many arguments to function