From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 13CF2A034F; Fri, 14 May 2021 13:58:53 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CA1B540042; Fri, 14 May 2021 13:58:52 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 9759C40041 for ; Fri, 14 May 2021 13:58:51 +0200 (CEST) IronPort-SDR: YRrOh3mHkMQbXUE2I+GIXBB80uYK6TECYAeA1OaTHc/zdf6Lji7Z6JurXoupgAGrAMAp1dXQu1 pY1tJd+fAv+g== X-IronPort-AV: E=McAfee;i="6200,9189,9983"; a="187576724" X-IronPort-AV: E=Sophos;i="5.82,299,1613462400"; d="scan'208";a="187576724" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 May 2021 04:58:45 -0700 IronPort-SDR: HbywSkZYUhAcm2dqY/RSSzZKT51smAHdWPgoGVWKQJ8z9WJ3JFL70LR5j5XIcUY40TGwEr6fYN vZ1hQVy43gRA== X-IronPort-AV: E=Sophos;i="5.82,299,1613462400"; d="scan'208";a="457123973" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.241.112]) ([10.213.241.112]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 May 2021 04:58:44 -0700 To: Heinrich Kuhn , dev@dpdk.org Cc: Simon Horman References: <20210514091934.64833-1-heinrich.kuhn@netronome.com> From: Ferruh Yigit X-User: ferruhy Message-ID: Date: Fri, 14 May 2021 12:58:39 +0100 MIME-Version: 1.0 In-Reply-To: <20210514091934.64833-1-heinrich.kuhn@netronome.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] net/nfp: fix internal NFP port addressing X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 5/14/2021 10:19 AM, Heinrich Kuhn wrote: > Depending on the breakout mode of the physical ports the internal NFP > port number might differ from the actual physical port number. Prior to > this patch the physical port number was used when making configuration > changes to the physical ports (enable, admin up etc). After this change > the internal port number is now correctly used for configuration > changes. > > Fixes: 5e15e799d ("net/nfp: create separate entity for PF device") > > Signed-off-by: Heinrich Kuhn > Signed-off-by: Simon Horman Applied to dpdk-next-net/main, thanks.