From: Jacob Keller <jacob.e.keller@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>, <davem@davemloft.net>,
<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>,
<netdev@vger.kernel.org>
Cc: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
<horms@kernel.org>, <ksundara@redhat.com>,
Wojciech Drewek <wojciech.drewek@intel.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH net 4/4] ice: use internal pf id instead of function number
Date: Tue, 20 Aug 2024 15:15:17 -0700 [thread overview]
Message-ID: <1875d5db-3960-45ae-97d9-ead2dca4769c@intel.com> (raw)
In-Reply-To: <20240820215620.1245310-5-anthony.l.nguyen@intel.com>
On 8/20/2024 2:56 PM, Tony Nguyen wrote:
> From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>
> Use always the same pf id in devlink port number. When doing
> pass-through the PF to VM bus info func number can be any value.
>
> Fixes: 2ae0aa4758b0 ("ice: Move devlink port to PF/VF struct")
> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
> Suggested-by: Jiri Pirko <jiri@resnulli.us>
> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-08-20 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 21:56 [PATCH net 0/4][pull request] Intel Wired LAN Driver Updates 2024-08-20 (ice) Tony Nguyen
2024-08-20 21:56 ` [PATCH net 1/4] ice: fix page reuse when PAGE_SIZE is over 8k Tony Nguyen
2024-08-20 22:10 ` Jacob Keller
2024-08-20 21:56 ` [PATCH net 2/4] ice: fix ICE_LAST_OFFSET formula Tony Nguyen
2024-08-20 22:14 ` Jacob Keller
2024-08-20 21:56 ` [PATCH net 3/4] ice: fix truesize operations for PAGE_SIZE >= 8192 Tony Nguyen
2024-08-20 22:12 ` Jacob Keller
2024-08-20 21:56 ` [PATCH net 4/4] ice: use internal pf id instead of function number Tony Nguyen
2024-08-20 22:15 ` Jacob Keller [this message]
2024-08-22 1:10 ` [PATCH net 0/4][pull request] Intel Wired LAN Driver Updates 2024-08-20 (ice) patchwork-bot+netdevbpf
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=1875d5db-3960-45ae-97d9-ead2dca4769c@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=ksundara@redhat.com \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wojciech.drewek@intel.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).