From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57671) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Xjx-0005Bi-FL for qemu-devel@nongnu.org; Thu, 18 Jun 2015 07:12:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5Xjs-0004xr-GH for qemu-devel@nongnu.org; Thu, 18 Jun 2015 07:12:13 -0400 Received: from mail-yh0-f51.google.com ([209.85.213.51]:35954) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5Xjs-0004xe-CD for qemu-devel@nongnu.org; Thu, 18 Jun 2015 07:12:08 -0400 Received: by yhan67 with SMTP id n67so53596877yha.3 for ; Thu, 18 Jun 2015 04:12:08 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20150618113745-mutt-send-email-mst@redhat.com> References: <1434620035-10808-1-git-send-email-kraxel@redhat.com> <1434620035-10808-2-git-send-email-kraxel@redhat.com> <20150618113745-mutt-send-email-mst@redhat.com> From: Peter Maydell Date: Thu, 18 Jun 2015 12:11:47 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PULL 1/1] virtio-input: evdev passthrough List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Gerd Hoffmann , QEMU Developers On 18 June 2015 at 10:39, Michael S. Tsirkin wrote: > On Thu, Jun 18, 2015 at 11:33:55AM +0200, Gerd Hoffmann wrote: >> +static Property virtio_input_host_pci_properties[] = { >> + DEFINE_VIRTIO_INPUT_PROPERTIES(VirtIOInputPCI, vdev.input), >> + DEFINE_PROP_STRING("evdev", VirtIOInputHostPCI, vdev.evdev), >> + DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 2), >> + DEFINE_PROP_END_OF_LIST(), >> +}; >> + > > Hmm I only noticed this now: I think properties > should all move into virtio input, there is > no reason to make them pci specific. 'vectors' is probably pci specific, but evdev isn't. > Since you already added some properties, it's ok > to apply this but please fix this with a patch on top. Shuffling properties around later while trying to maintain backcompat is painful, so I think we're better off just making sure we have them in the right places to start with. I'm dropping this pullreq from my queue. thanks -- PMM