From: Jerin Jacob <jerinjacobk@gmail.com>
To: Anoob Joseph <anoobj@marvell.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
Ashwin Sekhar T K <asekhar@marvell.com>,
Srikanth Yalavarthi <syalavarthi@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
dev@dpdk.org
Subject: Re: [PATCH] common/cnxk: restore segregation of logs based on module
Date: Mon, 27 May 2024 20:33:21 +0530 [thread overview]
Message-ID: <CALBAE1PGrbayO2h6n3ov0HXk78eDUZrg04Yk_wUyHUt8d-vXCA@mail.gmail.com> (raw)
In-Reply-To: <20240423104451.3018314-1-anoobj@marvell.com>
On Tue, Apr 23, 2024 at 4:15 PM Anoob Joseph <anoobj@marvell.com> wrote:
>
> Originally the logs were segregated under various labels which could be
> selectively enabled. It was changed to use 'pmd.common.cnxk' while
> changing the macro used for registering logging. Address the same by
> restoring the segregation.
>
> Current logs:
> ...
> logtype3
> pmd.common.cnxk
> pmd.common.iavf
> ...
>
> Changed to:
> ...
> logtype3
> pmd.common.cnxk.base
> pmd.common.cnxk.crypto
> pmd.common.cnxk.dpi
> pmd.common.cnxk.esw
> pmd.common.cnxk.event
> pmd.common.cnxk.flow
> pmd.common.cnxk.mbox
> pmd.common.cnxk.mempool
> pmd.common.cnxk.ml
> pmd.common.cnxk.nix
> pmd.common.cnxk.ree
> pmd.common.cnxk.rep
> pmd.common.cnxk.timer
> pmd.common.cnxk.tm
> pmd.common.iavf
> ...
>
> Updated documentation also to reflect the same.
>
> Fixes: 233692f550a1 ("dma/cnxk: rework DMA driver")
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
Applied to dpdk-next-net-mrvl/for-main. Thanks
prev parent reply other threads:[~2024-05-27 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:44 Anoob Joseph
2024-05-27 15:03 ` 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=CALBAE1PGrbayO2h6n3ov0HXk78eDUZrg04Yk_wUyHUt8d-vXCA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=syalavarthi@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).