DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] adjust mlx debug logs
Date: Tue, 16 Mar 2021 09:04:54 +0000	[thread overview]
Message-ID: <DM6PR12MB274852FFA60F0A0451E3FE8DCF6B9@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210309094836.988763-1-thomas@monjalon.net>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, March 9, 2021 11:49 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 0/4] adjust mlx debug logs
> 
> Few adjustments of debug log usage in mlx4/mlx5.
> 
> v2:
>     - fix a typo in an old log
>     - separate commit for line feed fixes (and fix more)
> 
> Thomas Monjalon (4):
>   net/mlx4: enable debug logs dynamically
>   common/mlx5: enable debug logs dynamically
>   common/mlx5: remove extra line feed in log messages
>   net/mlx5: reduce log level of alignment message
> 
>  drivers/common/mlx5/mlx5_common.h     |  2 --
>  drivers/common/mlx5/mlx5_common_mr.c  | 45 ++++++++++++++----------
> ---
>  drivers/common/mlx5/mlx5_common_pci.c |  4 +--
>  drivers/common/mlx5/mlx5_devx_cmds.c  |  2 +-
>  drivers/compress/mlx5/mlx5_compress.c |  2 +-
>  drivers/net/mlx4/mlx4_utils.h         |  5 ++-
>  drivers/net/mlx5/linux/mlx5_os.c      |  8 ++---
>  drivers/net/mlx5/linux/mlx5_verbs.c   | 13 ++++----
>  drivers/net/mlx5/mlx5_flow.c          |  2 +-
>  drivers/net/mlx5/mlx5_mr.c            | 12 +++----
>  drivers/net/mlx5/mlx5_rxq.c           | 11 ++++---
>  drivers/net/mlx5/mlx5_utils.c         |  4 +--
>  drivers/net/mlx5/windows/mlx5_os.c    |  2 +-
>  drivers/vdpa/mlx5/mlx5_vdpa.c         |  2 +-
>  14 files changed, 59 insertions(+), 55 deletions(-)
> 
> --
> 2.30.1

Series applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      parent reply	other threads:[~2021-03-16  9:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 22:28 [dpdk-dev] [PATCH 0/3] " Thomas Monjalon
2021-03-08 22:28 ` [dpdk-dev] [PATCH 1/3] net/mlx4: enable debug logs dynamically Thomas Monjalon
2021-03-08 22:28 ` [dpdk-dev] [PATCH 2/3] common/mlx5: " Thomas Monjalon
2021-03-08 22:28 ` [dpdk-dev] [PATCH 3/3] net/mlx5: reduce log level of alignment message Thomas Monjalon
2021-03-09  9:48 ` [dpdk-dev] [PATCH v2 0/4] adjust mlx debug logs Thomas Monjalon
2021-03-09  9:48   ` [dpdk-dev] [PATCH v2 1/4] net/mlx4: enable debug logs dynamically Thomas Monjalon
2021-03-11 20:03     ` Matan Azrad
2021-03-17 17:29     ` Ferruh Yigit
2021-03-17 17:47       ` Thomas Monjalon
2021-03-09  9:48   ` [dpdk-dev] [PATCH v2 2/4] common/mlx5: " Thomas Monjalon
2021-03-11 20:04     ` Matan Azrad
2021-03-17 17:39     ` Ferruh Yigit
2021-03-17 17:48       ` Thomas Monjalon
2021-03-18 10:13         ` Matan Azrad
2021-03-09  9:48   ` [dpdk-dev] [PATCH v2 3/4] common/mlx5: remove extra line feed in log messages Thomas Monjalon
2021-03-11 20:05     ` Matan Azrad
2021-03-09  9:48   ` [dpdk-dev] [PATCH v2 4/4] net/mlx5: reduce log level of alignment message Thomas Monjalon
2021-03-11 20:07     ` Matan Azrad
2021-03-16  9:04   ` 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=DM6PR12MB274852FFA60F0A0451E3FE8DCF6B9@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --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).