From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 28904A490 for ; Sat, 13 Jan 2018 23:50:02 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9748020C69; Sat, 13 Jan 2018 17:50:01 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 13 Jan 2018 17:50:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=9UxUJBoGTV1Hw4RnIAm2retGoh JFOjuieQSe7lxwFe8=; b=Ytc5ky7r862vqlhP6i0YrAETxdU6anoZJxUHpw7ocW i5pbZNCtN/kVuvlkTAJITE1cf5f+U34yx9XOOWn6m6uXciWgZBPADEsM/iskOWm9 +jh9Yy6vJbqXEBq2wIq1/eSU7kjAR60USDgLKnzL2f7lu02vW6FMYCR0MBKe/LV1 Y= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=9UxUJB oGTV1Hw4RnIAm2retGohJFOjuieQSe7lxwFe8=; b=fAulx2I0Dds0H2BkFQjQdq lXnOspfYokr1KNpAeN/VSdN6sK0UBfC/QUl0uORKxqiS/RfltIBy1Su7f4JfVzsX uaDK63A83HcqwaJmLtOG7tMqkzNw8sGdYZg4RGbPTqmhHeVriSLb/UK+aJ7+mNQc 88E/Fm2JjLxJBQj6ZHKwwGbiK0LKOK6ax+ca7znc8W+/8dmnt079/CV/uqK6OE3u lXUHzjEGIQRjWWijW/IIFL+TA9QoZGpppUku+dMSCXLPtJhhFwYR3NqqIc2sOcak vg3aW4vYep/uGJUj9CV3aY9d3YurTBvB891I3pwa0yiPADFQSrdu2pGgRsAhbjFA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4A9397E335; Sat, 13 Jan 2018 17:50:01 -0500 (EST) From: Thomas Monjalon To: "Burakov, Anatoly" , Jonas Pfefferle1 Cc: dev@dpdk.org Date: Sat, 13 Jan 2018 23:49:30 +0100 Message-ID: <2075027.JcYejM7RvO@xps> In-Reply-To: <45d1aa7c-2ceb-b6df-8e16-83ff1316cba1@intel.com> References: <1509465586-7436-1-git-send-email-jpf@zurich.ibm.com> <5559040.Nhk1psZjz2@xps> <45d1aa7c-2ceb-b6df-8e16-83ff1316cba1@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] vfio: noiommu check error handling 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: Sat, 13 Jan 2018 22:50:02 -0000 13/01/2018 13:15, Burakov, Anatoly: > On 11-Jan-18 11:45 PM, Thomas Monjalon wrote: > > 07/11/2017 10:50, Jonas Pfefferle1: > >>> Is there something urgent for 17.11? > >>> Or can it be refined in 18.02? > >> > >> Nothing urgent. We can refine this for 18.02. > >> > >>> Anatoly, any thought? > > > > Anatoly, Jonas, how do you want to proceed with this patch? > > > > I don't see anything to be refined here, it's a simple bug fix - code > assumes noiommu mode support is always available, when it might not be > the case on older kernels. As a bug fix, the title must start with "fix" and a tag "Fixes:" must be added to help with backport. At the same time, the explanation of the bug must be added in the commit log please. Thanks