From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>
Cc: hyonkim@cisco.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/enic: retain previous message logging
Date: Mon, 29 Jul 2019 12:03:09 +0100 [thread overview]
Message-ID: <82e2486c-e5ea-5ba0-a58a-962087da65c7@intel.com> (raw)
In-Reply-To: <20190726201246.26234-1-johndale@cisco.com>
On 7/26/2019 9:12 PM, John Daley wrote:
> Prior to the fix, RTE_LOGTYPE_INFO messages were displayed by default.
> After the fix, only NOTICE level and higher were displayed by default
> and INFO level were not. There are INFO level vNIC config related
> messages which customers and tech support currently depend on for
> debugging and so on and to suddenly hide these messages is not a good
> idea.
>
> This patch changes the default log level to RTE_LOG_INFO for enic so
> messages are printed as before the fix.
>
> Fixes: bbd8ecc05434 ("net/enic: remove PMD log type references")
>
> Signed-off-by: John Daley <johndale@cisco.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-07-29 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 2:46 [dpdk-dev] [PATCH] " John Daley
2019-07-25 10:07 ` Ferruh Yigit
2019-07-25 20:25 ` John Daley (johndale)
2019-07-26 4:21 ` Hyong Youb Kim (hyonkim)
2019-07-26 9:51 ` Ferruh Yigit
2019-07-26 20:50 ` Stephen Hemminger
2019-07-26 21:15 ` John Daley (johndale)
2019-07-26 8:17 ` John Daley (johndale)
2019-07-26 10:00 ` Ferruh Yigit
2019-07-26 20:06 ` John Daley (johndale)
2019-07-26 20:12 ` [dpdk-dev] [PATCH v2] " John Daley
2019-07-29 11:03 ` Ferruh Yigit [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=82e2486c-e5ea-5ba0-a58a-962087da65c7@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).