From: Yevgeny Kliteynik <kliteyn@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>, Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, Moshe Shemesh <moshe@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Vlad Dogaru <vdogaru@nvidia.com>,
Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH net-next 2/4] net/mlx5: HWS, make sure the uplink is the last destination
Date: Tue, 27 May 2025 02:11:55 +0300 [thread overview]
Message-ID: <bc1406b6-3082-4073-9523-b1bf35cb1908@nvidia.com> (raw)
In-Reply-To: <be4c5d3d-f2c9-4a09-96ec-0b25470ef9f7@redhat.com>
On 26-May-25 09:39, Paolo Abeni wrote:
> On 5/25/25 1:15 PM, Tariq Toukan wrote:
>> @@ -1429,6 +1426,14 @@ mlx5hws_action_create_dest_array(struct mlx5hws_context *ctx,
>> }
>> }
>>
>> + if (last_dest_idx != -1) {
>> + struct mlx5hws_cmd_set_fte_dest tmp;
>> +
>> + tmp = dest_list[last_dest_idx];
>> + dest_list[last_dest_idx] = dest_list[num_dest - 1];
>> + dest_list[num_dest - 1] = tmp;
>
> Here you can use swap()
Indeed, thanks.
-- YK
> /P
>
next prev parent reply other threads:[~2025-05-26 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 11:15 [PATCH net-next 0/4] net/mlx5: HWS, more fixes and adjustments Tariq Toukan
2025-05-25 11:15 ` [PATCH net-next 1/4] net/mlx5: HWS, fix missing ip_version handling in definer Tariq Toukan
2025-05-25 11:15 ` [PATCH net-next 2/4] net/mlx5: HWS, make sure the uplink is the last destination Tariq Toukan
2025-05-26 6:39 ` Paolo Abeni
2025-05-26 23:11 ` Yevgeny Kliteynik [this message]
2025-05-25 11:15 ` [PATCH net-next 3/4] net/mlx5: HWS, remove unused create_dest_array parameter Tariq Toukan
2025-05-25 11:15 ` [PATCH net-next 4/4] net/mlx5: HWS, remove incorrect comment Tariq Toukan
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=bc1406b6-3082-4073-9523-b1bf35cb1908@nvidia.com \
--to=kliteyn@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vdogaru@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).