From: Saeed Mahameed <saeed@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next V5 00/13] devlink, mlx5: Add new parameters for link management and SRIOV/eSwitch configurations
Date: Tue, 8 Jul 2025 20:04:30 -0700 [thread overview]
Message-ID: <aG3cPvni2Lhwye7R@x130> (raw)
In-Reply-To: <20250707162546.GN89747@horms.kernel.org>
On 07 Jul 17:25, Simon Horman wrote:
>On Sat, Jul 05, 2025 at 07:03:20PM -0700, Saeed Mahameed wrote:
>> From: Saeed Mahameed <saeedm@nvidia.com>
>>
>> This patch series introduces several devlink parameters improving device
>> configuration capabilities, link management, and SRIOV/eSwitch, by adding
>> NV config boot time parameters.
>
>...
>
>Thanks Saeed.
>
>Overall this patchset looks good to me.
>And, importantly, I believe review of earlier versions has been addressed.
>
>But unfortunately it does not apply cleanly against current net-next.
>Could you rebase?
Done, posting v6 now, Thanks Simon for the review.
next prev parent reply other threads:[~2025-07-09 3:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 2:03 [PATCH net-next V5 00/13] devlink, mlx5: Add new parameters for link management and SRIOV/eSwitch configurations Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 01/13] devlink: Add 'total_vfs' generic device param Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 02/13] net/mlx5: Implement cqe_compress_type via devlink params Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 03/13] net/mlx5: Implement devlink enable_sriov parameter Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 04/13] net/mlx5: Implement devlink total_vfs parameter Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 05/13] devlink: pass struct devlink_port * as arg to devlink_nl_param_fill() Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 06/13] devlink: Implement port params registration Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 07/13] devlink: Implement get/dump netlink commands for port params Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 08/13] devlink: Implement set netlink command " Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 09/13] devlink: Add 'keep_link_up' generic devlink device param Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 10/13] net/mlx5: Implement devlink keep_link_up port parameter Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 11/13] devlink: Throw extack messages on param value validation error Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 12/13] devlink: Implement devlink param multi attribute nested data values Saeed Mahameed
2025-07-06 2:03 ` [PATCH net-next V5 13/13] net/mlx5: Implement eSwitch hairpin per prio buffers devlink params Saeed Mahameed
2025-07-07 16:25 ` [PATCH net-next V5 00/13] devlink, mlx5: Add new parameters for link management and SRIOV/eSwitch configurations Simon Horman
2025-07-09 3:04 ` Saeed Mahameed [this message]
2025-07-09 8:38 ` Simon Horman
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=aG3cPvni2Lhwye7R@x130 \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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