From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] common/mlx5: align driver name logs across pmds
Date: Tue, 30 Mar 2021 07:35:57 +0000 [thread overview]
Message-ID: <DM6PR12MB375368581AB475931E227748DF7D9@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1615842355-10526-1-git-send-email-michaelba@nvidia.com>
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Monday, March 15, 2021 23:06
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> Raslan Darawsheh <rasland@nvidia.com>; Asaf Penso <asafp@nvidia.com>
> Subject: [PATCH 1/2] common/mlx5: align driver name logs across pmds
>
> From: Asaf Penso <asafp@nvidia.com>
>
> Some mlx5 pmds define the log prefix as "mlx5_pmd" while others as
> "pmd_mlx5".
> The patch aligns all pmds to use the "mlx5_pmd" format.
>
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-03-30 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 21:05 Michael Baum
2021-03-15 21:05 ` [dpdk-dev] [PATCH 2/2] common/mlx5: rename driver name to include PCI notation Michael Baum
2021-03-30 7:36 ` Slava Ovsiienko
2021-03-30 7:35 ` Slava Ovsiienko [this message]
2021-04-01 11:30 ` [dpdk-dev] [PATCH 1/2] common/mlx5: align driver name logs across pmds 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=DM6PR12MB375368581AB475931E227748DF7D9@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
/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).