From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMIUo-00084q-Vc for qemu-devel@nongnu.org; Fri, 13 Feb 2015 10:49:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMIUl-0003cK-BQ for qemu-devel@nongnu.org; Fri, 13 Feb 2015 10:49:34 -0500 Received: from mail-bn1bon0147.outbound.protection.outlook.com ([157.56.111.147]:15968 helo=na01-bn1-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMIUl-0003c6-5p for qemu-devel@nongnu.org; Fri, 13 Feb 2015 10:49:31 -0500 Message-ID: <54DE1945.30600@freescale.com> Date: Fri, 13 Feb 2015 17:33:25 +0200 From: Vasile Catalin-B50542 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [vhost] link new devices List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org How does the vhost API links with vhost devices? I don't see any "*-net" or "*_net" or even "*net" references in vhost API files, nor do I see any registering macros inside vhost-net device code.