From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 2A6A82BD3 for ; Tue, 16 Oct 2018 14:55:57 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B9ECF22274; Tue, 16 Oct 2018 08:55:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 16 Oct 2018 08:55:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=ijHCCwdOJ39I2ILqs7T1j4qEdBjlsJD0z/J6PMGZ7Z0=; b=EBB8tP3fKwWt VUNnsteOlgjbNL8jBIk9sS6YrLsfY4scu/IoC+Ysy8qqJpaszlMFlGsjjIcTohQf 1XNYaap/CMp6tnNiuq4yfypVgZ4MQR5inyJj3jYaejckR4AWsoDwyOrTu6bhbLeA zKy+MXr5lA8KDhNi+7ySWcSbn9Kxpx8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=ijHCCwdOJ39I2ILqs7T1j4qEdBjlsJD0z/J6PMGZ7 Z0=; b=L4LWkUfCpw6fqOPllm7kMhyAdPKjP0cEgJP5WRxAvM4rIKRTB/JxOSGMb 0w8TeRHFnU/EiExPOW3fZ09ML/ckWAlza4nVS0dFR4mV3txVxMhY30J9FEw7iCBu SY1yoYmZCoOOBulNhaflmXe7hGYZ/Qs0NWzaai9avmRlSTvmQgEVzV4hwDcYi+s/ 2wUcvyiTObiaWkrKsw2wkOC16ig5hkhLObj4qnDW4ea9fXhPzYoagWmMtjjtQM2N 5YlJBSGOx2qURrxP8T6aoUAw9bok5e4b28hS8IEIeTQULMeZDVFQ6vEIo4UiifAb j/pzLRRNlie7XtYiO9o88Kq7OEb6Q== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BB3E0102F0; Tue, 16 Oct 2018 08:55:55 -0400 (EDT) From: Thomas Monjalon To: Jeff Guo Cc: Ferruh Yigit , anatoly.burakov@intel.com, dev@dpdk.org Date: Tue, 16 Oct 2018 14:55:58 +0200 Message-ID: <13173016.DHzOh1Wy4B@xps> In-Reply-To: <10ce3595-ea26-59a5-e4ab-d3780edde2f3@intel.com> References: <1539690153-133112-1-git-send-email-jia.guo@intel.com> <10ce3595-ea26-59a5-e4ab-d3780edde2f3@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH 2/2] vfio: fix build issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 12:55:57 -0000 16/10/2018 14:52, Ferruh Yigit: > On 10/16/2018 12:42 PM, Jeff Guo wrote: > > Since the older kernel version do not implement the device request > > interface for vfio, so when build on the kernel < v4.0.0, which is > > the version begin to add the device request interface, it will > > throw the error to show =E2=80=9CVFIO_PCI_REQ_IRQ_INDEX=E2=80=9D is und= eclared. > > This patch aim to fix this compile issue by add the macro > > =E2=80=9CHAVE_VFIO_DEV_REQ_INTERFACE=E2=80=9D after checking the kernel= version. > >=20 > > Signed-off-by: Jeff Guo >=20 > Fixes: 0eb8a1c4c786 ("vfio: add request notifier interrupt") > Fixes: c115fd000c32 ("vfio: handle hotplug request notifier") >=20 > Reviewed-by: Ferruh Yigit Series applies, thanks