DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Gregory Etelson <getelson@nvidia.com>
Subject: RE: [PATCH] common/mlx5: replace use of PMD logtype
Date: Mon, 6 Mar 2023 13:19:29 +0000	[thread overview]
Message-ID: <DM6PR12MB37530692B1E25E7867501882DFB69@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230223174127.189231-1-stephen@networkplumber.org>

Hi, Stephen

We have another place of using RTE_LOG in mlx5_glue_path().
Should we update this one as well ?

With best regards,
Slava


> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: четверг, 23 февраля 2023 г. 19:41
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Gregory
> Etelson <getelson@nvidia.com>
> Subject: [PATCH] common/mlx5: replace use of PMD logtype
> 
> The goal to eliminate the generic PMD logtype.
> One place it is used unnecessarily is in the mlx5 common code.
> Change the one RTE_LOG() call here to use the same macro as other log
> messages in same file.
> 
> Fixes: 9c410b28b27a ("common/mlx5: refactor HCA attributes query")
> Cc: viacheslavo@nvidia.com
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  drivers/common/mlx5/mlx5_devx_cmds.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/common/mlx5/mlx5_devx_cmds.c
> b/drivers/common/mlx5/mlx5_devx_cmds.c
> index fb670950ef64..710649f86533 100644
> --- a/drivers/common/mlx5/mlx5_devx_cmds.c
> +++ b/drivers/common/mlx5/mlx5_devx_cmds.c
> @@ -543,7 +543,7 @@ mlx5_devx_cmd_query_hca_vdpa_attr(void *ctx,
>  			MLX5_GET_HCA_CAP_OP_MOD_VDPA_EMULATION
> |
>  			MLX5_HCA_CAP_OPMOD_GET_CUR);
>  	if (!hcattr) {
> -		RTE_LOG(DEBUG, PMD, "Failed to query devx VDPA
> capabilities");
> +		DRV_LOG(DEBUG, "Failed to query devx VDPA capabilities");
>  		vdpa_attr->valid = 0;
>  	} else {
>  		vdpa_attr->valid = 1;
> --
> 2.39.1


  reply	other threads:[~2023-03-06 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 17:41 Stephen Hemminger
2023-03-06 13:19 ` Slava Ovsiienko [this message]
2023-06-13 14:18   ` David Marchand
2023-08-21 14:32 ` [PATCH v2] " Stephen Hemminger
2023-08-21 16:16 ` [PATCH v3] " Stephen Hemminger
2023-08-21 16:25   ` Tyler Retzlaff
2023-09-25  7:17   ` 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=DM6PR12MB37530692B1E25E7867501882DFB69@DM6PR12MB3753.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).