From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id B9B521B748 for ; Tue, 24 Oct 2017 09:38:45 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4F50C20EB1; Tue, 24 Oct 2017 03:38:45 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 24 Oct 2017 03:38:45 -0400 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=Z56dX+rLFQJrL6kAk/SE6prK44 vk8dQMm8LX+s/ld8E=; b=BP7wsEO1ZLeMDne4QvOsi0W1jIyV+HNAMBitd0MKRn 7mI5dTxo8cZ85AStI8pENfcnajP68Yz64h64YK2Xv7FxzreXNNlUYgt/j37FEemK Aij1SSOr5YvVI1dvCZHHRzIaMjiNVcNDqTn7zzJZhcnUFqDwmMIZ6tGwlinQuhE9 E= 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=Z56dX+ rLFQJrL6kAk/SE6prK44vk8dQMm8LX+s/ld8E=; b=C+z3yMw3YaCCO7vc7+ZckY WPN/sVok1zMRnPTb1LLovbR49iZo9GhEilRaGeWBcKKbtiYaa2aU7po7Yh/5UZ7D qbnS/nUuFvHDbv1BBwHIhpiH2wATfF0EO3oYUqJBmqUoZLSpXzup4BHdwR8UvkvN yvW5PpH6DvAlPmq26N8b2KGm91m20egsIpxMHVIdouI2hNIUJU4cBNJ8r4KyVqhC 8p79cA96V/AHeIpDXYUtUNnHZ99BtmyNyeAyqdtdCd9p441QYpc613d/nZtYkcpv iWBlHxCAsSNqZUDduFtc8hZmqQppgKMRa2prL/DwRtRfnTB1CcQNGbtWpa2BqCgg == 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 01E177F91B; Tue, 24 Oct 2017 03:38:45 -0400 (EDT) From: Thomas Monjalon To: santosh Cc: dev@dpdk.org, olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, anatoly.burakov@intel.com Date: Tue, 24 Oct 2017 09:38:43 +0200 Message-ID: <1834369.xF2sHLYOla@xps> In-Reply-To: References: <20170905103119.20511-1-santosh.shukla@caviumnetworks.com> <8773955.bCW0FxgjuB@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3 0/6] make dpdk iova aware 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, 24 Oct 2017 07:38:45 -0000 24/10/2017 07:12, santosh: > Hi Thomas, > > > On Monday 23 October 2017 08:28 PM, Thomas Monjalon wrote: > > 20/10/2017 14:31, Santosh Shukla: > >> v3: > >> Include v2 review comment and rebased on > >> top of upstream tip commit:6b9ed026a8704 > >> > >> > >> v2: > >> Include build fixes reported in patchworks. > > Please fix checkpatch issues, thanks > > > Checkpatch warning coming from legacy code, not from iova change, > Same mentioned down in cover letter. > Will address them in v4.. After we conclude on your proposition on [5/6] patch of this series. Sorry, I had overlooked checkpatch issues. No need to fix the checkpatch issues if it makes code lines formatted differently of their context.