From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rakesh Kudurumalla <rkudurumalla@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>,
dev@dpdk.org, jerinj@marvell.com
Subject: Re: [PATCH v2 1/1] common/cnxk: fix updated loglevel from NOTICE to INFO
Date: Thu, 3 Oct 2024 15:47:12 +0530 [thread overview]
Message-ID: <CALBAE1MddeZwh6ycT_06tOX74nnUAEr8C7S+3XABE3v5MVkMCw@mail.gmail.com> (raw)
In-Reply-To: <20241001084710.608200-1-rkudurumalla@marvell.com>
On Tue, Oct 1, 2024 at 2:24 PM Rakesh Kudurumalla
<rkudurumalla@marvell.com> wrote:
>
> In latest dpdk PMD log type is removed and driver
> specific log type is added for CNXK. This patch
> changes loglevel of CNXK from NOTICE to INFO
> to display logs while running applications
>
> Fixes: 455a771fd6f1 ("common/cnxk: fix segregation of logs based on module")
>
> Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-main. Thanks
common/cnxk: fix loglevel from NOTICE to INFO
In a247fcd94598 changeset, the PMD log type is removed and
driver specific log type is added for CNXK.
This patch changes loglevel of CNXK from NOTICE to INFO
to display logs while running applications
Fixes: a247fcd94598 ("drivers: use dedicated log macros instead of
PMD logtype")
Cc: stable@dpdk.org
Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
prev parent reply other threads:[~2024-10-03 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 6:24 [PATCH 1/1] common/cnxk: updated loglevel from NOTICE to INFO Rakesh Kudurumalla
2024-09-19 18:09 ` Jerin Jacob
2024-10-01 8:47 ` [PATCH v2 1/1] common/cnxk: fix " Rakesh Kudurumalla
2024-10-03 10:17 ` 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=CALBAE1MddeZwh6ycT_06tOX74nnUAEr8C7S+3XABE3v5MVkMCw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rkudurumalla@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).