From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, madhu.chittim@intel.com,
aleksander.lobakin@intel.com, horms@kernel.org,
bhelgaas@google.com, linux-pci@vger.kernel.org,
sridhar.samudrala@intel.com, aleksandr.loktionov@intel.com,
marek.landowski@intel.com
Subject: Re: [PATCH net-next] idpf: add support for IDPF PCI programming interface
Date: Thu, 06 Nov 2025 14:50:06 +0000 [thread overview]
Message-ID: <176244060675.238839.11553624450020733973.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251103224631.595527-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 3 Nov 2025 14:46:30 -0800 you wrote:
> From: Pavan Kumar Linga <pavan.kumar.linga@intel.com>
>
> At present IDPF supports only 0x1452 and 0x145C as PF and VF device IDs
> on our current generation hardware. Future hardware exposes a new set of
> device IDs for each generation. To avoid adding a new device ID for each
> generation and to make the driver forward and backward compatible,
> make use of the IDPF PCI programming interface to load the driver.
>
> [...]
Here is the summary with links:
- [net-next] idpf: add support for IDPF PCI programming interface
https://git.kernel.org/netdev/net-next/c/13068e9d5726
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-11-06 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 22:46 [PATCH net-next] idpf: add support for IDPF PCI programming interface Tony Nguyen
2025-11-04 17:17 ` Simon Horman
2025-11-06 14:50 ` 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=176244060675.238839.11553624450020733973.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=madhu.chittim@intel.com \
--cc=marek.landowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sridhar.samudrala@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).