From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 1AEB58DEA for ; Mon, 22 Dec 2014 02:22:53 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP; 21 Dec 2014 17:21:04 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,691,1406617200"; d="scan'208";a="502392594" Received: from pgsmsx105.gar.corp.intel.com ([10.221.44.96]) by orsmga003.jf.intel.com with ESMTP; 21 Dec 2014 17:18:17 -0800 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by PGSMSX105.gar.corp.intel.com (10.221.44.96) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 22 Dec 2014 09:21:15 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.110]) by shsmsx102.ccr.corp.intel.com ([169.254.2.216]) with mapi id 14.03.0195.001; Mon, 22 Dec 2014 09:21:13 +0800 From: "Qiu, Michael" To: Thomas Monjalon Thread-Topic: [PATCH v6] VFIO: Avoid to enable vfio while the module not loaded Thread-Index: AQHQFG78U6g7aYyFH06BPZipKqjrIg== Date: Mon, 22 Dec 2014 01:21:13 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E60286CA19A4@SHSMSX101.ccr.corp.intel.com> References: <1418035455-9434-1-git-send-email-michael.qiu@intel.com> <533710CFB86FA344BFBF2D6802E60286CA1227@SHSMSX101.ccr.corp.intel.com> <4162168.RCAhVMLdi5@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v6] VFIO: Avoid to enable vfio while the module not loaded X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Dec 2014 01:22:55 -0000 On 12/19/2014 4:24 PM, Thomas Monjalon wrote:=0A= > 2014-12-19 07:09, Qiu, Michael:=0A= >> Hi Thomas,=0A= >>=0A= >> Will you plan to merge this patch? If yes, you plan to merge it into= =0A= >> 1.8 or 2.0?=0A= > It won't be in 1.8 for 2 reasons:=0A= > - there is a risk to break something in some environments, so need more = tests=0A= > - you add a function protoype in eal common without bsd implementation=0A= =0A= OK, fair enough, I check with you just as a reminder to be ensure that=0A= you do not miss this thread.=0A= =0A= =0A=