From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] doc: fix incorrect example for specifying log level
Date: Wed, 18 Mar 2020 08:57:55 +0800 [thread overview]
Message-ID: <20200318005754.GB51165@intel.com> (raw)
In-Reply-To: <20200317101805.4a3f6827@hermes.lan>
On 03/17, Stephen Hemminger wrote:
>On Tue, 17 Mar 2020 16:31:06 +0800
>Xiaolong Ye <xiaolong.ye@intel.com> wrote:
>
>> Now we need to add prefix like lib. to enable the log.
>>
>> Fixes: ffb9fd1b0808 ("log: update legacy modules dynamic logs regex")
>> Cc: stable@dpdk.org
>>
>> Reported-by: Haiyue Wang <haiyue.wang@intel.com>
>> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
>> ---
>> doc/guides/linux_gsg/eal_args.include.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/doc/guides/linux_gsg/eal_args.include.rst b/doc/guides/linux_gsg/eal_args.include.rst
>> index ed8b0e35b..b48b23927 100644
>> --- a/doc/guides/linux_gsg/eal_args.include.rst
>> +++ b/doc/guides/linux_gsg/eal_args.include.rst
>> @@ -132,7 +132,7 @@ Debugging options
>>
>> Specify log level for a specific component. For example::
>>
>> - --log-level eal:8
>> + --log-level lib.eal:8
>>
>> Can be specified multiple times.
>>
>
>Please change numeric value to name as well. Recent versions of
>DPDK allow "debug" instead of 8
Make sense, will update it.
Thanks,
Xiaolong
next prev parent reply other threads:[~2020-03-18 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 8:31 [dpdk-stable] " Xiaolong Ye
2020-03-17 17:18 ` [dpdk-stable] [dpdk-dev] " Stephen Hemminger
2020-03-18 0:57 ` Ye Xiaolong [this message]
2020-03-18 0:58 ` [dpdk-stable] [PATCH v2] " Xiaolong Ye
2020-04-26 20:25 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=20200318005754.GB51165@intel.com \
--to=xiaolong.ye@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--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).