From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Yevgeny Kliteynik <kliteyn@nvidia.com>
Subject: [net-next V2 06/14] net/mlx5: DR, Fix code indentation
Date: Mon, 21 Aug 2023 10:57:31 -0700 [thread overview]
Message-ID: <20230821175739.81188-7-saeed@kernel.org> (raw)
In-Reply-To: <20230821175739.81188-1-saeed@kernel.org>
From: Yevgeny Kliteynik <kliteyn@nvidia.com>
Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
---
drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c b/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c
index feb307fb3440..14f6df88b1f9 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/steering/fs_dr.c
@@ -336,7 +336,7 @@ static int mlx5_cmd_dr_create_fte(struct mlx5_flow_root_namespace *ns,
if (fte->action.pkt_reformat->owner == MLX5_FLOW_RESOURCE_OWNER_FW) {
err = -EINVAL;
mlx5dr_err(domain, "FW-owned reformat can't be used in SW rule\n");
- goto free_actions;
+ goto free_actions;
}
is_decap = fte->action.pkt_reformat->reformat_type ==
--
2.41.0
next prev parent reply other threads:[~2023-08-21 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 17:57 [pull request][net-next V2 00/14] mlx5 updates 2023-08-16 Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 01/14] net/mlx5e: aRFS, Prevent repeated kernel rule migrations requests Saeed Mahameed
2023-08-22 18:10 ` patchwork-bot+netdevbpf
2023-08-21 17:57 ` [net-next V2 02/14] net/mlx5e: aRFS, Warn if aRFS table does not exist for aRFS rule Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 03/14] net/mlx5e: aRFS, Introduce ethtool stats Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 04/14] net/mlx5e: Fix spelling mistake "Faided" -> "Failed" Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 05/14] net/mlx5: IRQ, consolidate irq and affinity mask allocation Saeed Mahameed
2023-08-21 17:57 ` Saeed Mahameed [this message]
2023-08-21 17:57 ` [net-next V2 07/14] net/mlx5: DR, Remove unneeded local variable Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 08/14] net/mlx5: Remove health syndrome enum duplication Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 09/14] net/mlx5: Update dead links in Kconfig documentation Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 10/14] net/mlx5: Call mlx5_esw_offloads_rep_load/unload() for uplink port directly Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 11/14] net/mlx5: Remove VPORT_UPLINK handling from devlink_port.c Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 12/14] net/mlx5: Rename devlink port ops struct for PFs/VFs Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 13/14] net/mlx5: DR, Supporting inline WQE when possible Saeed Mahameed
2023-08-21 17:57 ` [net-next V2 14/14] net/mlx5: Devcom, only use devcom after NULL check in mlx5_devcom_send_event() 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=20230821175739.81188-7-saeed@kernel.org \
--to=saeed@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=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).