From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Mody, Rasesh" <Rasesh.Mody@cavium.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/bnx2x: cleanup info logs
Date: Tue, 27 Nov 2018 15:30:23 +0000 [thread overview]
Message-ID: <abf96a1a-2fb3-cf98-4616-596a96a901a9@intel.com> (raw)
In-Reply-To: <1542447449-19888-1-git-send-email-rasesh.mody@cavium.com>
On 11/17/2018 9:37 AM, Mody, Rasesh wrote:
> Reduced number of INFO logs in BNX2X PMD by converting some INFO
> logs to DEBUG and few NOTICE logs to INFO, removing extra new lines,
> printing banner bar once for the adapter and device specific info.
>
> Fixes: ba7eeb035a5f ("net/bnx2x: fix logging to include device name")
> Fixes: 540a211084a7 ("bnx2x: driver core")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2018-11-27 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 18:17 [dpdk-dev] [PATCH " Mody, Rasesh
2018-11-14 18:17 ` [dpdk-dev] [PATCH 2/2] net/bnx2x: bump version to 1.0.7.1 Mody, Rasesh
2018-11-16 11:26 ` [dpdk-dev] [PATCH 1/2] net/bnx2x: cleanup info logs Ferruh Yigit
2018-11-17 9:38 ` Mody, Rasesh
2018-11-17 9:37 ` [dpdk-dev] [PATCH v2 " Mody, Rasesh
2018-11-27 15:30 ` Ferruh Yigit [this message]
2018-11-17 9:37 ` [dpdk-dev] [PATCH v2 2/2] net/bnx2x: bump version to 1.0.7.1 Mody, Rasesh
2018-11-19 13:27 ` Ferruh Yigit
2018-11-19 18:48 ` Mody, Rasesh
2018-11-20 9:22 ` Ferruh Yigit
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=abf96a1a-2fb3-cf98-4616-596a96a901a9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
/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).