From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH] common/cnxk: update NIX and NPA dump function
Date: Sun, 23 Jan 2022 18:48:21 +0530 [thread overview]
Message-ID: <CALBAE1Pp=AdnUC0cpCvMjZ+EzU7CTrkRjtVfvo4xoW1hXHQL8A@mail.gmail.com> (raw)
In-Reply-To: <20211220132625.13496-1-rbhansali@marvell.com>
On Mon, Dec 20, 2021 at 6:56 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> Updates nix_dump and npa_dump to use plt_dump function.
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks
> ---
> drivers/common/cnxk/roc_nix_debug.c | 4 ++--
> drivers/common/cnxk/roc_npa_debug.c | 2 +-
> drivers/common/cnxk/roc_platform.h | 1 +
> 3 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/common/cnxk/roc_nix_debug.c b/drivers/common/cnxk/roc_nix_debug.c
> index 266935a6c5..7466f782c3 100644
> --- a/drivers/common/cnxk/roc_nix_debug.c
> +++ b/drivers/common/cnxk/roc_nix_debug.c
> @@ -5,14 +5,14 @@
> #include "roc_api.h"
> #include "roc_priv.h"
>
> -#define nix_dump(fmt, ...) fprintf(stderr, fmt "\n", ##__VA_ARGS__)
> +#define nix_dump plt_dump
> #define NIX_REG_INFO(reg) \
> { \
> reg, #reg \
> }
> #define NIX_REG_NAME_SZ 48
>
> -#define nix_dump_no_nl(fmt, ...) fprintf(stderr, fmt, ##__VA_ARGS__)
> +#define nix_dump_no_nl plt_dump_no_nl
>
> struct nix_lf_reg_info {
> uint32_t offset;
> diff --git a/drivers/common/cnxk/roc_npa_debug.c b/drivers/common/cnxk/roc_npa_debug.c
> index 421c2af8a5..798ace291c 100644
> --- a/drivers/common/cnxk/roc_npa_debug.c
> +++ b/drivers/common/cnxk/roc_npa_debug.c
> @@ -5,7 +5,7 @@
> #include "roc_api.h"
> #include "roc_priv.h"
>
> -#define npa_dump(fmt, ...) fprintf(stderr, fmt "\n", ##__VA_ARGS__)
> +#define npa_dump plt_dump
>
> static inline void
> npa_pool_dump(__io struct npa_pool_s *pool)
> diff --git a/drivers/common/cnxk/roc_platform.h b/drivers/common/cnxk/roc_platform.h
> index 61d4781209..13b23cec03 100644
> --- a/drivers/common/cnxk/roc_platform.h
> +++ b/drivers/common/cnxk/roc_platform.h
> @@ -204,6 +204,7 @@ extern int cnxk_logtype_tm;
> #define plt_warn(fmt, args...) RTE_LOG(WARNING, PMD, fmt "\n", ##args)
> #define plt_print(fmt, args...) RTE_LOG(INFO, PMD, fmt "\n", ##args)
> #define plt_dump(fmt, ...) fprintf(stderr, fmt "\n", ##__VA_ARGS__)
> +#define plt_dump_no_nl(fmt, ...) fprintf(stderr, fmt, ##__VA_ARGS__)
>
> /**
> * Log debug message if given subsystem logging is enabled.
> --
> 2.25.1
>
prev parent reply other threads:[~2022-01-23 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 13:26 Rahul Bhansali
2022-01-23 13:18 ` Jerin Jacob [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='CALBAE1Pp=AdnUC0cpCvMjZ+EzU7CTrkRjtVfvo4xoW1hXHQL8A@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rbhansali@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).