From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org, Olivier MATZ <olivier.matz@6wind.com>,
ferruh.yigit@intel.com
Subject: Re: [PATCH v2 3/3] logs: remove log level config option
Date: Wed, 17 Jan 2018 14:22:51 +0100 [thread overview]
Message-ID: <10267387.yn3KPbUsfK@xps> (raw)
In-Reply-To: <20171212163620.pphb6ioehmze2oje@platinum>
12/12/2017 17:36, Olivier MATZ:
> On Sat, Dec 09, 2017 at 06:53:58PM +0530, Pavan Nikhilesh wrote:
> > Remove RTE_LOG_LEVEL config option, use existing RTE_LOG_DP_LEVEL config
> > option for controlling datapath log level.
> > RTE_LOG_LEVEL is no longer needed as dynamic logging can be used to
> > control global and module specific log levels.
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
Series applied, thanks
prev parent reply other threads:[~2018-01-17 13:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 9:28 [PATCH 1/3] eal: update legacy modules dynamic logs regex Pavan Nikhilesh
2017-11-22 9:28 ` [PATCH 2/3] eal: update default log levels Pavan Nikhilesh
2017-12-07 13:15 ` Olivier MATZ
2017-11-22 9:28 ` [PATCH 3/3] logs: remove log level config option Pavan Nikhilesh
2017-12-07 13:21 ` Olivier MATZ
2017-12-07 14:07 ` Pavan Nikhilesh Bhagavatula
2017-12-08 15:37 ` Olivier MATZ
2017-11-22 22:57 ` [PATCH 1/3] eal: update legacy modules dynamic logs regex Ferruh Yigit
2017-12-07 13:14 ` Olivier MATZ
2017-12-09 13:23 ` [PATCH v2 " Pavan Nikhilesh
2017-12-09 13:23 ` [PATCH v2 2/3] eal: update default log levels Pavan Nikhilesh
2017-12-09 13:23 ` [PATCH v2 3/3] logs: remove log level config option Pavan Nikhilesh
2017-12-12 16:36 ` Olivier MATZ
2018-01-12 15:46 ` Thomas Monjalon
2018-01-12 15:52 ` Pavan Nikhilesh
2018-01-12 16:08 ` Thomas Monjalon
2018-01-17 13:22 ` 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=10267387.yn3KPbUsfK@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=pbhagavatula@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.