From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
jianfeng.tan@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/6] eal: fix default log level
Date: Thu, 20 Apr 2017 01:31:57 +0200 [thread overview]
Message-ID: <2283020.bQNkVTF6HB@xps> (raw)
In-Reply-To: <7319eb94-1541-de04-2f8b-e5542f90701c@intel.com>
18/04/2017 17:29, Ferruh Yigit:
> On 4/18/2017 3:22 PM, Olivier Matz wrote:
> > The initialization of the default log level (from configuration) was
> > removed by mistake in a previous commit. The global log level was
> > wrongly set to debug when no --log-level argument was passed. Restore
> > this initialization.
> >
> > Before:
> > $ ./build/app/test
> > RTE>>dump_log_types
> > global log level is debug
> > ...
> >
> > After:
> > $ ./build/app/test
> > RTE>>dump_log_types
> > global log level is info
> > ...
> >
> > Fixes: 845afe51e428 ("eal: change specific log levels at startup")
> >
> > Reported-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
>
> Series Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series Applied, thanks
prev parent reply other threads:[~2017-04-19 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 14:22 Olivier Matz
2017-04-18 14:22 ` [dpdk-dev] [PATCH 2/6] eal: move internal config initialization Olivier Matz
2017-04-18 14:22 ` [dpdk-dev] [PATCH 3/6] eal: remove log level from internal config Olivier Matz
2017-04-18 15:00 ` Ferruh Yigit
2017-04-18 15:26 ` Olivier MATZ
2017-04-18 15:28 ` Ferruh Yigit
2017-04-18 14:22 ` [dpdk-dev] [PATCH 4/6] eal: remove undue printf Olivier Matz
2017-04-18 14:22 ` [dpdk-dev] [PATCH 5/6] eal: fix log level regexp matching Olivier Matz
2017-04-18 14:22 ` [dpdk-dev] [PATCH 6/6] eal: fix dump of registered logs when disabled Olivier Matz
2017-04-18 15:29 ` [dpdk-dev] [PATCH 1/6] eal: fix default log level Ferruh Yigit
2017-04-19 23:31 ` Thomas Monjalon [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=2283020.bQNkVTF6HB@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=olivier.matz@6wind.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).