From: Ratheesh Kannoth <rkannoth@marvell.com>
To: <netdev-bot+sashiko@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<sgoutham@marvell.com>, <sbhatta@marvell.com>
Subject: Re: [PATCH net-next] octeontx2-af: fix PF/CGX debugfs PCI bus lookup
Date: Fri, 4 Sep 2026 14:14:20 +0530 [thread overview]
Message-ID: <apqE5CT5_M4coO0m@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <178850836833.4131868.13905270816601203708@kernel.org>
On 2026-09-04 at 13:22:48, netdev-bot+sashiko@kernel.org (netdev-bot+sashiko@kernel.org) wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential
> issue(s) to consider:
>
> Critical: 0 · High: 0 · Medium: 2 · Low: 1
>
> - [Medium] rvu_dbg_rvu_pf_cgx_map_display()
> (drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c) now derives…
> - [Medium] The patch fixes only one of the driver's PF→PCI-device
> conversions, leaving the same 'RVU PF n is on bus n + 1' assumption in…
> - [Low] The commit fixes a user-visible debugfs defect (the
> rvu_pf_cgx_map file silently omitted every mapped PF when the AF was…
>
> --
>
> octeontx2-af: fix PF/CGX debugfs PCI bus lookup
>
> The rvu_pf_cgx_map debugfs file looked up each RVU PF PCI device assuming
> PF0 always lives on PCI bus 1. This commit takes the base bus number from
> rvu->pdev->bus->number instead, so the per-PF lookup uses pf + start.
will address in v2
pw-bot: changes-requested
prev parent reply other threads:[~2026-09-04 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 4:49 Ratheesh Kannoth
2026-09-04 7:52 ` netdev-bot+sashiko
2026-09-04 8:44 ` Ratheesh Kannoth [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=apqE5CT5_M4coO0m@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@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
all inboxes | Powered by JetHome®