From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Heinrich Kuhn <heinrich.kuhn@netronome.com>, dev@dpdk.org
Cc: Simon Horman <simon.horman@netronome.com>
Subject: Re: [dpdk-dev] [PATCH] net/nfp: fix internal NFP port addressing
Date: Fri, 14 May 2021 12:58:39 +0100 [thread overview]
Message-ID: <e06e76c3-7575-8ae1-6bc9-8e6b95bd8ad9@intel.com> (raw)
In-Reply-To: <20210514091934.64833-1-heinrich.kuhn@netronome.com>
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 <heinrich.kuhn@netronome.com>
> Signed-off-by: Simon Horman <simon.horman@netronome.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-05-14 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 9:19 Heinrich Kuhn
2021-05-14 11:58 ` Ferruh Yigit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e06e76c3-7575-8ae1-6bc9-8e6b95bd8ad9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=heinrich.kuhn@netronome.com \
--cc=simon.horman@netronome.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).