From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 0/6] make dpdk iova aware Date: Tue, 24 Oct 2017 09:38:43 +0200 Message-ID: <1834369.xF2sHLYOla@xps> References: <20170905103119.20511-1-santosh.shukla@caviumnetworks.com> <8773955.bCW0FxgjuB@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, olivier.matz@6wind.com, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com, anatoly.burakov@intel.com To: santosh 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) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.