From: Simon Horman <horms@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, sgoutham@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com
Subject: Re: [net-next PATCH 3/3] octeontx2-af: Cleanup loopback device checks
Date: Thu, 25 Jan 2024 11:34:04 +0000 [thread overview]
Message-ID: <20240125113404.GH217708@kernel.org> (raw)
In-Reply-To: <20240124055014.32694-4-gakula@marvell.com>
On Wed, Jan 24, 2024 at 11:20:14AM +0530, Geetha sowjanya wrote:
> PCI device IDs of RVU device IDs are configurable and
> RVU PF0's (ie AF's) are currently assumed as VFs that
> identify loopback functionality ie LBKVFs. But in some
> cases these VFs can be setup for different functionality.
> Hence remove assumptions that AF's VFs are always LBK VFs
> by renaming 'is_afvf' as 'is_lbkvf' explicitly and also
> identify LBK VF using PCI dev ID. Similar change is done
> for other VF types.
>
> Signed-off-by: Geetha sowjanya <gakula@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-01-25 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 5:50 [net-next PATCH 0/3] Dynamically allocate BPIDs Geetha sowjanya
2024-01-24 5:50 ` [net-next PATCH 1/3] octeontx2-af: Create BPIDs free pool Geetha sowjanya
2024-01-25 11:33 ` Simon Horman
2024-01-26 9:52 ` [EXT] " Geethasowjanya Akula
2024-01-24 5:50 ` [net-next PATCH 2/3] octeontx2-af: Add mbox to alloc/free BPIDs Geetha sowjanya
2024-01-25 11:33 ` Simon Horman
2024-01-24 5:50 ` [net-next PATCH 3/3] octeontx2-af: Cleanup loopback device checks Geetha sowjanya
2024-01-25 11:34 ` Simon Horman [this message]
2024-01-26 2:16 ` [net-next PATCH 0/3] Dynamically allocate BPIDs Jakub Kicinski
2024-01-26 9:54 ` [EXT] " Geethasowjanya Akula
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=20240125113404.GH217708@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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).