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 D600C1BD37 for ; Fri, 11 May 2018 11:00:35 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4D3B321412; Fri, 11 May 2018 05:00:35 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 11 May 2018 05:00:35 -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=WQFor8ciOS8MzFw9bWmy6xKWCH EUtbWylgjmqK1We3o=; b=QWgMBsSflVXgN9GUfgqfMLYTG4uO3tJfb+IT7A3xkD /w6eQPHSjpPwYy6dM3WY4tokW2H/fxXU54wDj8q564BOhHTVgdAe+Zgl3TrqLuXV ESoCSv/ONxHLbkRu7H1bGfDptBDyOriV475V66vYnc8miJqTVdIA8L3zNvAlZuI7 c= 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=fm2; bh=WQFor8 ciOS8MzFw9bWmy6xKWCHEUtbWylgjmqK1We3o=; b=Kxncruafv4mM0qtbcBMnn+ xVzdwcU+jXxDiBhLOUaAutG20tWofDUcCpwwySutp8MzhN1hyiac3AuqCbfyslC5 9SU46S7Gb/l39LZL6xa1jnSpYaaD/i5bZ1akUYXThj8ah17+nLVhhafxJjS3+2XW fydrIcCQk4EaaEpeh1RQH529cYXBL6ozZROxnrtzTMJNBtIFPcaMh3vsdyG3KwIJ B37tuADx6PlzxxGy9u//CIdauGUPr4lx7LN3ZsJ3POkw6mcarzbDdNW43q/8oOf3 iSHLP7SlXtfsPMEs/KSdoHLhwQCNegWi7shhuGBxlzAA5UR0+rNyf9nHQhF7Ve9w == 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 54500E4350; Fri, 11 May 2018 05:00:34 -0400 (EDT) From: Thomas Monjalon To: Lei Cc: dev@dpdk.org, Ferruh Yigit , nikhil.rao@intel.com, jerin.jacob@cavium.com Date: Fri, 11 May 2018 11:00:32 +0200 Message-ID: <2342302.sue3H7Idtu@xps> In-Reply-To: <33b05f1b-5425-0648-d1c2-31cd01d79d67@intel.com> References: <1525789656-4173-1-git-send-email-lei.a.yao@intel.com> <33b05f1b-5425-0648-d1c2-31cd01d79d67@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eventdev: change port_id to uint16_t 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: Fri, 11 May 2018 09:00:36 -0000 10/05/2018 21:59, Ferruh Yigit: > On 5/8/2018 3:27 PM, Lei wrote: > > From: yao > > > > From 17.11, port_id is changed from uint8_t to uint16_t.But in eventdev, > > it still use the old fashion. This patch fix this issue. > > > > Signed-off-by: Lei Yao > > Acked-by: Ferruh Yigit > > This issue also cause build error when CONFIG_RTE_MAX_ETHPORTS more than 255 > > More detail related the build error can be found at: > https://dpdk.org/dev/patchwork/patch/39658/ Another patch was been pushed in next-eventdev: https://dpdk.org/dev/patchwork/patch/39706/