From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/2] Type-safe ioport callbacks Date: Sun, 24 Oct 2010 19:38:42 +0200 Message-ID: <4CC46F22.7070202@redhat.com> References: <1287934469-16624-1-git-send-email-avi@redhat.com> <4CC46E73.2090704@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42178 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932203Ab0JXRis (ORCPT ); Sun, 24 Oct 2010 13:38:48 -0400 In-Reply-To: <4CC46E73.2090704@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/24/2010 07:35 PM, Paolo Bonzini wrote: > On 10/24/2010 05:34 PM, Avi Kivity wrote: >> A recent qemu -> qemu-kvm merge broke cpu hotplug without the compiler >> complaining because of the type-unsafeness of the ioport callbacks. >> This >> patchset adds a type-safe variant of ioport callbacks and coverts a >> sample >> ioport. Converting the other 300-odd registrations is left as an >> excercise >> to the community. > > Should we create a Documentation/ file with incomplete transitions and > the commit(s) that introduced them, for volunteers who wish to do some > dirty work or to learn Coccinelle? If we have a TODO, we could add a janitor section there. -- error compiling committee.c: too many arguments to function