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, kliteyn@nvidia.com, valex@nvidia.com
Subject: Re: [net-next 01/15] net/mlx5: DR, Move ACTION_CACHE_LINE_SIZE macro to header
Date: Mon, 17 Apr 2023 07:20:22 +0000 [thread overview]
Message-ID: <168171602229.1935.5518330974522513366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230414220939.136865-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Fri, 14 Apr 2023 15:09:25 -0700 you wrote:
> From: Yevgeny Kliteynik <kliteyn@nvidia.com>
>
> Move ACTION_CACHE_LINE_SIZE macro to header to be used by
> the pattern functions as well.
>
> Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
> Reviewed-by: Alex Vesker <valex@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> [...]
Here is the summary with links:
- [net-next,01/15] net/mlx5: DR, Move ACTION_CACHE_LINE_SIZE macro to header
https://git.kernel.org/netdev/net-next/c/b47dddc624ef
- [net-next,02/15] net/mlx5: DR, Add cache for modify header pattern
https://git.kernel.org/netdev/net-next/c/da5d0027d666
- [net-next,03/15] net/mlx5: DR, Split chunk allocation to HW-dependent ways
https://git.kernel.org/netdev/net-next/c/2533e726f472
- [net-next,04/15] net/mlx5: DR, Check for modify_header_argument device capabilities
https://git.kernel.org/netdev/net-next/c/b7ba743a2f1c
- [net-next,05/15] net/mlx5: DR, Add create/destroy for modify-header-argument general object
https://git.kernel.org/netdev/net-next/c/de69696b6eee
- [net-next,06/15] net/mlx5: DR, Add support for writing modify header argument
https://git.kernel.org/netdev/net-next/c/4605fc0a2b65
- [net-next,07/15] net/mlx5: DR, Read ICM memory into dedicated buffer
https://git.kernel.org/netdev/net-next/c/7d7c9453d679
- [net-next,08/15] net/mlx5: DR, Fix QP continuous allocation
https://git.kernel.org/netdev/net-next/c/17dc71c336aa
- [net-next,09/15] net/mlx5: DR, Add modify header arg pool mechanism
https://git.kernel.org/netdev/net-next/c/608d4f1769d8
- [net-next,10/15] net/mlx5: DR, Add modify header argument pointer to actions attributes
https://git.kernel.org/netdev/net-next/c/0caebadda57b
- [net-next,11/15] net/mlx5: DR, Apply new accelerated modify action and decapl3
https://git.kernel.org/netdev/net-next/c/62e40c856825
- [net-next,12/15] net/mlx5: DR, Support decap L3 action using pattern / arg mechanism
https://git.kernel.org/netdev/net-next/c/947e258537ea
- [net-next,13/15] net/mlx5: DR, Modify header action of size 1 optimization
https://git.kernel.org/netdev/net-next/c/40ff097f2503
- [net-next,14/15] net/mlx5: DR, Add support for the pattern/arg parameters in debug dump
https://git.kernel.org/netdev/net-next/c/a21e52bb8f37
- [net-next,15/15] net/mlx5: DR, Enable patterns and arguments for supporting devices
https://git.kernel.org/netdev/net-next/c/220ae987838c
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-04-17 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 22:09 [pull request][net-next 00/15] mlx5 updates 2023-04-14 Saeed Mahameed
2023-04-14 22:09 ` [net-next 01/15] net/mlx5: DR, Move ACTION_CACHE_LINE_SIZE macro to header Saeed Mahameed
2023-04-17 7:20 ` patchwork-bot+netdevbpf [this message]
2023-04-14 22:09 ` [net-next 02/15] net/mlx5: DR, Add cache for modify header pattern Saeed Mahameed
2023-04-14 22:09 ` [net-next 03/15] net/mlx5: DR, Split chunk allocation to HW-dependent ways Saeed Mahameed
2023-04-14 22:09 ` [net-next 04/15] net/mlx5: DR, Check for modify_header_argument device capabilities Saeed Mahameed
2023-04-14 22:09 ` [net-next 05/15] net/mlx5: DR, Add create/destroy for modify-header-argument general object Saeed Mahameed
2023-04-14 22:09 ` [net-next 06/15] net/mlx5: DR, Add support for writing modify header argument Saeed Mahameed
2023-04-14 22:09 ` [net-next 07/15] net/mlx5: DR, Read ICM memory into dedicated buffer Saeed Mahameed
2023-04-14 22:09 ` [net-next 08/15] net/mlx5: DR, Fix QP continuous allocation Saeed Mahameed
2023-04-14 22:09 ` [net-next 09/15] net/mlx5: DR, Add modify header arg pool mechanism Saeed Mahameed
2023-04-14 22:09 ` [net-next 10/15] net/mlx5: DR, Add modify header argument pointer to actions attributes Saeed Mahameed
2023-04-14 22:09 ` [net-next 11/15] net/mlx5: DR, Apply new accelerated modify action and decapl3 Saeed Mahameed
2023-04-14 22:09 ` [net-next 12/15] net/mlx5: DR, Support decap L3 action using pattern / arg mechanism Saeed Mahameed
2023-04-14 22:09 ` [net-next 13/15] net/mlx5: DR, Modify header action of size 1 optimization Saeed Mahameed
2023-04-14 22:09 ` [net-next 14/15] net/mlx5: DR, Add support for the pattern/arg parameters in debug dump Saeed Mahameed
2023-04-14 22:09 ` [net-next 15/15] net/mlx5: DR, Enable patterns and arguments for supporting devices 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=168171602229.1935.5518330974522513366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=valex@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).