All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, rsaladi2@marvell.com,
	sbhatta@marvell.com, sgoutham@marvell.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH v2 net] octeontx2-af: fix PF/CGX debugfs PCI bus lookup
Date: Thu, 10 Sep 2026 15:20:04 +0000	[thread overview]
Message-ID: <178905360439.1492964.17732959701772223922.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260904085114.3385530-1-rkannoth@marvell.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 4 Sep 2026 14:21:13 +0530 you wrote:
> rvu_dbg_rvu_pf_cgx_map_display() locates each RVU PF PCI device via
> pci_get_domain_bus_and_slot() when printing the PF-to-CGX map. It
> assumed PF0 always sits on PCI bus 1 and derived other PF bus numbers
> as pf + 1, but the AF device can be enumerated on a different bus.
> 
> Use rvu->pdev->bus->number as the base bus instead, so each PF lookup
> uses pf + start on systems where RVU functions are on contiguous buses
> but do not start at bus 1.
> 
> [...]

Here is the summary with links:
  - [v2,net] octeontx2-af: fix PF/CGX debugfs PCI bus lookup
    https://git.kernel.org/netdev/net/c/4f4b743c2d2b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-10 15:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  8:51 [PATCH v2 net] octeontx2-af: fix PF/CGX debugfs PCI bus lookup Ratheesh Kannoth
2026-09-10  2:53 ` netdev-bot+sashiko
2026-09-10  3:02   ` Ratheesh Kannoth
2026-09-10  9:38     ` Simon Horman
2026-09-10 15:20 ` patchwork-bot+netdevbpf [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=178905360439.1492964.17732959701772223922.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=rsaladi2@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.