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, joshua.a.hay@intel.com,
madhu.chittim@intel.com, samuel.salin@intel.com
Subject: Re: [PATCH net-next v2 00/10][pull request] refactor IDPF resource access
Date: Sun, 25 Jan 2026 23:20:15 +0000 [thread overview]
Message-ID: <176938321560.4010024.11653612290613271910.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122223601.2208759-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Thu, 22 Jan 2026 14:35:46 -0800 you wrote:
> Pavan Kumar Linga says:
>
> Queue and vector resources for a given vport, are stored in the
> idpf_vport structure. At the time of configuration, these
> resources are accessed using vport pointer. Meaning, all the
> config path functions are tied to the default queue and vector
> resources of the vport.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/10] idpf: introduce local idpf structure to store virtchnl queue chunks
https://git.kernel.org/netdev/net-next/c/d83d80347dea
- [net-next,v2,02/10] idpf: introduce idpf_q_vec_rsrc struct and move vector resources to it
https://git.kernel.org/netdev/net-next/c/d1061502f353
- [net-next,v2,03/10] idpf: move queue resources to idpf_q_vec_rsrc structure
https://git.kernel.org/netdev/net-next/c/502eccecce5f
- [net-next,v2,04/10] idpf: move some iterator declarations inside for loops
https://git.kernel.org/netdev/net-next/c/f6892116be91
- [net-next,v2,05/10] idpf: reshuffle idpf_vport struct members to avoid holes
https://git.kernel.org/netdev/net-next/c/47ee0543a450
- [net-next,v2,06/10] idpf: add rss_data field to RSS function parameters
https://git.kernel.org/netdev/net-next/c/cfa7029a2500
- [net-next,v2,07/10] idpf: remove vport pointer from queue sets
https://git.kernel.org/netdev/net-next/c/9ad94c235aa6
- [net-next,v2,08/10] idpf: generalize send virtchnl message API
https://git.kernel.org/netdev/net-next/c/601643400bbb
- [net-next,v2,09/10] idpf: avoid calling get_rx_ptypes for each vport
https://git.kernel.org/netdev/net-next/c/822cd0923344
- [net-next,v2,10/10] idpf: generalize mailbox API
https://git.kernel.org/netdev/net-next/c/086d030e99d2
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:[~2026-01-25 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 22:35 [PATCH net-next v2 00/10][pull request] refactor IDPF resource access Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 01/10] idpf: introduce local idpf structure to store virtchnl queue chunks Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 02/10] idpf: introduce idpf_q_vec_rsrc struct and move vector resources to it Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 03/10] idpf: move queue resources to idpf_q_vec_rsrc structure Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 04/10] idpf: move some iterator declarations inside for loops Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 05/10] idpf: reshuffle idpf_vport struct members to avoid holes Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 06/10] idpf: add rss_data field to RSS function parameters Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 07/10] idpf: remove vport pointer from queue sets Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 08/10] idpf: generalize send virtchnl message API Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 09/10] idpf: avoid calling get_rx_ptypes for each vport Tony Nguyen
2026-01-22 22:35 ` [PATCH net-next v2 10/10] idpf: generalize mailbox API Tony Nguyen
2026-01-25 23: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=176938321560.4010024.11653612290613271910.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samuel.salin@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