From: patchwork-bot+netdevbpf@kernel.org
To: Hariprasad Kelam <hkelam@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, sgoutham@marvell.com,
gakula@marvell.com, jerinj@marvell.com, lcherian@marvell.com,
sbhatta@marvell.com, naveenm@marvell.com, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch
Subject: Re: [net-next] Octeontx2-af: RPM: Register driver with PCI subsys IDs
Date: Wed, 26 Feb 2025 03:10:50 +0000 [thread overview]
Message-ID: <174053945024.217003.8404388361563873866.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224035603.1220913-1-hkelam@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Feb 2025 09:26:03 +0530 you wrote:
> Although the PCI device ID and Vendor ID for the RPM (MAC) block
> have remained the same across Octeon CN10K and the next-generation
> CN20K silicon, Hardware architecture has changed (NIX mapped RPMs
> and RFOE Mapped RPMs).
>
> Add PCI Subsystem IDs to the device table to ensure that this driver
> can be probed from NIX mapped RPM devices only.
>
> [...]
Here is the summary with links:
- [net-next] Octeontx2-af: RPM: Register driver with PCI subsys IDs
https://git.kernel.org/netdev/net-next/c/fc9167192f29
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-26 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 3:56 [net-next] Octeontx2-af: RPM: Register driver with PCI subsys IDs Hariprasad Kelam
2025-02-26 3:10 ` 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=174053945024.217003.8404388361563873866.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=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--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