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, rrameshbabu@nvidia.com, jiri@nvidia.com,
gal@nvidia.com
Subject: Re: [net-next 01/14] net/mlx5: Consolidate devlink documentation in devlink/mlx5.rst
Date: Wed, 16 Aug 2023 02:40:25 +0000 [thread overview]
Message-ID: <169215362520.5089.13536736279401930023.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230814214144.159464-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Saeed Mahameed <saeedm@nvidia.com>:
On Mon, 14 Aug 2023 14:41:31 -0700 you wrote:
> From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
>
> De-duplicate documentation by removing mellanox/mlx5/devlink.rst. Instead,
> only use the generic devlink documentation directory to document mlx5
> devlink parameters. Avoid providing general devlink tool usage information
> in mlx5-specific documentation.
>
> [...]
Here is the summary with links:
- [net-next,01/14] net/mlx5: Consolidate devlink documentation in devlink/mlx5.rst
https://git.kernel.org/netdev/net-next/c/b608dd670bb6
- [net-next,02/14] net/mlx5e: Make tx_port_ts logic resilient to out-of-order CQEs
https://git.kernel.org/netdev/net-next/c/3178308ad4ca
- [net-next,03/14] net/mlx5e: Add recovery flow for tx devlink health reporter for unhealthy PTP SQ
https://git.kernel.org/netdev/net-next/c/53b836a44db4
- [net-next,04/14] net/mlx5: Expose max possible SFs via devlink resource
https://git.kernel.org/netdev/net-next/c/6486c0f44ed8
- [net-next,05/14] net/mlx5: Check with FW that sync reset completed successfully
https://git.kernel.org/netdev/net-next/c/a9f168e4c6e1
- [net-next,06/14] net/mlx5: E-switch, Add checking for flow rule destinations
https://git.kernel.org/netdev/net-next/c/e0e22d59b47a
- [net-next,07/14] net/mlx5: Use auxiliary_device_uninit() instead of device_put()
https://git.kernel.org/netdev/net-next/c/2ad0160c02be
- [net-next,08/14] net/mlx5: Remove redundant SF supported check from mlx5_sf_hw_table_init()
https://git.kernel.org/netdev/net-next/c/ae80d7a06fdb
- [net-next,09/14] net/mlx5: Use mlx5_sf_start_function_id() helper instead of directly calling MLX5_CAP_GEN()
https://git.kernel.org/netdev/net-next/c/88074d81e5fe
- [net-next,10/14] net/mlx5: Remove redundant check of mlx5_vhca_event_supported()
https://git.kernel.org/netdev/net-next/c/b63f8bde2fba
- [net-next,11/14] net/mlx5: Fix error message in mlx5_sf_dev_state_change_handler()
https://git.kernel.org/netdev/net-next/c/36e5a0efc810
- [net-next,12/14] net/mlx5: Remove unused CAPs
https://git.kernel.org/netdev/net-next/c/0b4eb603d635
- [net-next,13/14] net/mlx5: Remove unused MAX HCA capabilities
https://git.kernel.org/netdev/net-next/c/a41cb59117fa
- [net-next,14/14] net/mlx5: Don't query MAX caps twice
https://git.kernel.org/netdev/net-next/c/bd3a2f77809b
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-08-16 2:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 21:41 [pull request][net-next 00/14] mlx5 updates 2023-08-14 Saeed Mahameed
2023-08-14 21:41 ` [net-next 01/14] net/mlx5: Consolidate devlink documentation in devlink/mlx5.rst Saeed Mahameed
2023-08-16 2:40 ` patchwork-bot+netdevbpf [this message]
2023-08-14 21:41 ` [net-next 02/14] net/mlx5e: Make tx_port_ts logic resilient to out-of-order CQEs Saeed Mahameed
2023-08-14 21:41 ` [net-next 03/14] net/mlx5e: Add recovery flow for tx devlink health reporter for unhealthy PTP SQ Saeed Mahameed
2023-08-14 21:41 ` [net-next 04/14] net/mlx5: Expose max possible SFs via devlink resource Saeed Mahameed
2023-08-14 21:41 ` [net-next 05/14] net/mlx5: Check with FW that sync reset completed successfully Saeed Mahameed
2023-08-14 21:41 ` [net-next 06/14] net/mlx5: E-switch, Add checking for flow rule destinations Saeed Mahameed
2023-08-14 21:41 ` [net-next 07/14] net/mlx5: Use auxiliary_device_uninit() instead of device_put() Saeed Mahameed
2023-08-14 21:41 ` [net-next 08/14] net/mlx5: Remove redundant SF supported check from mlx5_sf_hw_table_init() Saeed Mahameed
2023-08-14 21:41 ` [net-next 09/14] net/mlx5: Use mlx5_sf_start_function_id() helper instead of directly calling MLX5_CAP_GEN() Saeed Mahameed
2023-08-14 21:41 ` [net-next 10/14] net/mlx5: Remove redundant check of mlx5_vhca_event_supported() Saeed Mahameed
2023-08-14 21:41 ` [net-next 11/14] net/mlx5: Fix error message in mlx5_sf_dev_state_change_handler() Saeed Mahameed
2023-08-14 21:41 ` [net-next 12/14] net/mlx5: Remove unused CAPs Saeed Mahameed
2023-08-14 21:41 ` [net-next 13/14] net/mlx5: Remove unused MAX HCA capabilities Saeed Mahameed
2023-08-14 21:41 ` [net-next 14/14] net/mlx5: Don't query MAX caps twice 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=169215362520.5089.13536736279401930023.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rrameshbabu@nvidia.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).