From: Shahaf Shuler <shahafs@mellanox.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Yongseok Koh" <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: clean-up developer logs
Date: Thu, 21 Jun 2018 10:57:54 +0000 [thread overview]
Message-ID: <DB7PR05MB4426FD931EC6CF6FA0D1DBD2C3760@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <69ffd267bbac6399ea20a8d56fef9bb8fad2095f.1528188147.git.nelio.laranjeiro@6wind.com>
Tuesday, June 5, 2018 11:45 AM, Nelio Laranjeiro:
> Subject: [dpdk-dev] [PATCH v2] net/mlx5: clean-up developer logs
>
> Split maintainers logs from user logs.
>
> A lot of debug logs are present providing internal information on how the
> PMD works to users. Such logs should not be available for them and thus
> should remain available only when the PMD is compiled in debug mode.
>
> This commits removes some useless debug logs, move the Maintainers ones
> under DEBUG and also move dump into debug mode only.
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>
> ---
>
> Changes in v2:
>
> remove even more developer logs.
> ---
> drivers/net/mlx5/mlx5_mr.c | 119 +++++++++++++++-----------------
> drivers/net/mlx5/mlx5_mr.h | 5 +-
> drivers/net/mlx5/mlx5_rxq.c | 56 +--------------
> drivers/net/mlx5/mlx5_trigger.c | 2 -
> drivers/net/mlx5/mlx5_txq.c | 18 +----
> 5 files changed, 62 insertions(+), 138 deletions(-)
>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-06-21 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 9:43 [dpdk-dev] [PATCH] " Nelio Laranjeiro
2018-06-05 8:45 ` [dpdk-dev] [PATCH v2] " Nelio Laranjeiro
2018-06-21 10:57 ` Shahaf Shuler [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=DB7PR05MB4426FD931EC6CF6FA0D1DBD2C3760@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=yskoh@mellanox.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).