From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, leonro@nvidia.com, maxtram95@gmail.com
Subject: Re: [net 01/12] net/mlx5e: XDP, Allow growing tail for XDP multi buffer
Date: Mon, 19 Jun 2023 09:40:22 +0000 [thread overview]
Message-ID: <168716762233.17662.6686641236588648870.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230616200119.44163-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Fri, 16 Jun 2023 13:01:08 -0700 you wrote:
> From: Maxim Mikityanskiy <maxtram95@gmail.com>
>
> The cited commits missed passing frag_size to __xdp_rxq_info_reg, which
> is required by bpf_xdp_adjust_tail to support growing the tail pointer
> in fragmented packets. Pass the missing parameter when the current RQ
> mode allows XDP multi buffer.
>
> [...]
Here is the summary with links:
- [net,01/12] net/mlx5e: XDP, Allow growing tail for XDP multi buffer
https://git.kernel.org/netdev/net/c/4e7401fc8c8d
- [net,02/12] net/mlx5e: xsk: Set napi_id to support busy polling on XSK RQ
https://git.kernel.org/netdev/net/c/62a522d3354d
- [net,03/12] net/mlx5: Fix driver load with single msix vector
https://git.kernel.org/netdev/net/c/0ab999d4a1bf
- [net,04/12] net/mlx5e: TC, Add null pointer check for hardware miss support
https://git.kernel.org/netdev/net/c/b100573ab76e
- [net,05/12] net/mlx5e: TC, Cleanup ct resources for nic flow
https://git.kernel.org/netdev/net/c/fb7be476ab7e
- [net,06/12] net/mlx5: DR, Support SW created encap actions for FW table
https://git.kernel.org/netdev/net/c/87cd0649176c
- [net,07/12] net/mlx5: DR, Fix wrong action data allocation in decap action
https://git.kernel.org/netdev/net/c/ef4c5afc783d
- [net,08/12] net/mlx5: Free IRQ rmap and notifier on kernel shutdown
https://git.kernel.org/netdev/net/c/314ded538e5f
- [net,09/12] net/mlx5e: Don't delay release of hardware objects
https://git.kernel.org/netdev/net/c/cf5bb02320d4
- [net,10/12] net/mlx5e: Fix ESN update kernel panic
https://git.kernel.org/netdev/net/c/fef06678931f
- [net,11/12] net/mlx5e: Drop XFRM state lock when modifying flow steering
https://git.kernel.org/netdev/net/c/c75b94255aaa
- [net,12/12] net/mlx5e: Fix scheduling of IPsec ASO query while in atomic
https://git.kernel.org/netdev/net/c/a128f9d4c122
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-06-19 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 20:01 [pull request][net 00/12] mlx5 fixes 2023-06-16 Saeed Mahameed
2023-06-16 20:01 ` [net 01/12] net/mlx5e: XDP, Allow growing tail for XDP multi buffer Saeed Mahameed
2023-06-19 9:40 ` patchwork-bot+netdevbpf [this message]
2023-06-16 20:01 ` [net 02/12] net/mlx5e: xsk: Set napi_id to support busy polling on XSK RQ Saeed Mahameed
2023-06-16 20:01 ` [net 03/12] net/mlx5: Fix driver load with single msix vector Saeed Mahameed
2023-06-16 20:01 ` [net 04/12] net/mlx5e: TC, Add null pointer check for hardware miss support Saeed Mahameed
2023-06-16 20:01 ` [net 05/12] net/mlx5e: TC, Cleanup ct resources for nic flow Saeed Mahameed
2023-06-16 20:01 ` [net 06/12] net/mlx5: DR, Support SW created encap actions for FW table Saeed Mahameed
2023-06-16 20:01 ` [net 07/12] net/mlx5: DR, Fix wrong action data allocation in decap action Saeed Mahameed
2023-06-16 20:01 ` [net 08/12] net/mlx5: Free IRQ rmap and notifier on kernel shutdown Saeed Mahameed
2023-06-16 20:01 ` [net 09/12] net/mlx5e: Don't delay release of hardware objects Saeed Mahameed
2023-06-16 20:01 ` [net 10/12] net/mlx5e: Fix ESN update kernel panic Saeed Mahameed
2023-06-16 20:01 ` [net 11/12] net/mlx5e: Drop XFRM state lock when modifying flow steering Saeed Mahameed
2023-06-16 20:01 ` [net 12/12] net/mlx5e: Fix scheduling of IPsec ASO query while in atomic Saeed Mahameed
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=168716762233.17662.6686641236588648870.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=maxtram95@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).