From: Raslan Darawsheh <rasland@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>
Subject: RE: [PATCH v3] common/mlx5: replace use of PMD logtype
Date: Mon, 25 Sep 2023 07:17:20 +0000 [thread overview]
Message-ID: <MN0PR12MB6056E2D99EC2BC95609FB8B9CFFCA@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230821161625.413827-1-stephen@networkplumber.org>
Hi,
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Monday, August 21, 2023 7:16 PM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Gregory
> Etelson <getelson@nvidia.com>
> Subject: [PATCH v3] 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>
> ---
> v3 - also address use in glue code
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-09-25 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 17:41 [PATCH] " Stephen Hemminger
2023-03-06 13:19 ` Slava Ovsiienko
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 [this message]
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=MN0PR12MB6056E2D99EC2BC95609FB8B9CFFCA@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=suanmingm@nvidia.com \
--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).