DPDK patches and discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>, Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Erez Shitrit <erezsh@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/mlx5/hws: fix typo in the log
Date: Mon, 13 Nov 2023 07:51:29 +0000	[thread overview]
Message-ID: <CO6PR12MB5396A3D78974E377E47D7AC9C1B3A@CO6PR12MB5396.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231113072051.6748-1-bingz@nvidia.com>

Hi,

> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Monday, November 13, 2023 3:21 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Suanming
> Mou <suanmingm@nvidia.com>; Ori Kam <orika@nvidia.com>
> Cc: dev@dpdk.org; Erez Shitrit <erezsh@nvidia.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5/hws: fix typo in the log
> 
> Change "cureent" to "current".
> 
> Fixes: fa16fead9a68 ("net/mlx5/hws: support rule update after its creation")
> Cc: erezsh@nvidia.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Bing Zhao <bingz@nvidia.com>

Acked-by: Suanming Mou <suanmingm@nvidia.com>

> ---
>  drivers/net/mlx5/hws/mlx5dr_rule.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/hws/mlx5dr_rule.c
> b/drivers/net/mlx5/hws/mlx5dr_rule.c
> index 980a99b226..fa19303b91 100644
> --- a/drivers/net/mlx5/hws/mlx5dr_rule.c
> +++ b/drivers/net/mlx5/hws/mlx5dr_rule.c
> @@ -741,7 +741,7 @@ int mlx5dr_rule_action_update(struct mlx5dr_rule
> *rule_handle,
> 
>  	if (unlikely(mlx5dr_table_is_root(matcher->tbl) ||
>  	    unlikely(mlx5dr_matcher_req_fw_wqe(matcher)))) {
> -		DR_LOG(ERR, "Rule update not supported on cureent matcher");
> +		DR_LOG(ERR, "Rule update not supported on current matcher");
>  		rte_errno = ENOTSUP;
>  		return -rte_errno;
>  	}
> --
> 2.34.1


  reply	other threads:[~2023-11-13  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  7:20 Bing Zhao
2023-11-13  7:51 ` Suanming Mou [this message]
2023-11-14  8:12 ` Raslan Darawsheh

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=CO6PR12MB5396A3D78974E377E47D7AC9C1B3A@CO6PR12MB5396.namprd12.prod.outlook.com \
    --to=suanmingm@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=erezsh@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@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).