From: Roi Dayan <roid@nvidia.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Oz Shlomo <ozsh@nvidia.com>,
<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] net/mlx5e: Fix spelling mistake "supoported" -> "supported"
Date: Tue, 1 Feb 2022 09:43:18 +0200 [thread overview]
Message-ID: <2df0d488-36c9-1f2b-8d27-7ada36ad3f4f@nvidia.com> (raw)
In-Reply-To: <20220131084317.8058-1-colin.i.king@gmail.com>
On 2022-01-31 10:43 AM, Colin Ian King wrote:
> There is a spelling mistake in a NL_SET_ERR_MSG_MOD error
> message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ct.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ct.c b/drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ct.c
> index 85f0cb88127f..9fb1a9a8bc02 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ct.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ct.c
> @@ -21,7 +21,7 @@ tc_act_can_offload_ct(struct mlx5e_tc_act_parse_state *parse_state,
> }
>
> if (parse_state->ct && !clear_action) {
> - NL_SET_ERR_MSG_MOD(extack, "Multiple CT actions are not supoported");
> + NL_SET_ERR_MSG_MOD(extack, "Multiple CT actions are not supported");
> return false;
> }
>
thanks
you can add a fixes line if needed
Fixes: fd7ab32d19b6 ("net/mlx5e: TC, Reject rules with multiple CT actions")
Reviewed-by: Roi Dayan <roid@nvidia.com>
next prev parent reply other threads:[~2022-02-01 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:43 Colin Ian King
2022-02-01 7:43 ` Roi Dayan [this message]
2022-02-02 4:31 ` 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=2df0d488-36c9-1f2b-8d27-7ada36ad3f4f@nvidia.com \
--to=roid@nvidia.com \
--cc=colin.i.king@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=saeedm@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
all inboxes | Powered by JetHome®