From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 3/5] eal: make eal_log_level save private
Date: Wed, 25 Apr 2018 01:55:25 +0200 [thread overview]
Message-ID: <1676287.Xq9lriP4j0@xps> (raw)
In-Reply-To: <20180424165808.23292-4-stephen@networkplumber.org>
24/04/2018 18:58, Stephen Hemminger:
> +int rte_eal_log_save_regexp(const char *regex, int tmp)
The prefix rte_log_ is preferred over rte_eal_log_.
next prev parent reply other threads:[~2018-04-24 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:58 [dpdk-dev] [PATCH v2 0/5] logging enhancements Stephen Hemminger
2018-04-24 16:58 ` [dpdk-dev] [PATCH v2 1/5] eal: make syslog facility table const Stephen Hemminger
2018-04-24 16:58 ` [dpdk-dev] [PATCH v2 2/5] eal: allow symbolic log levels Stephen Hemminger
2018-04-24 16:58 ` [dpdk-dev] [PATCH v2 3/5] eal: make eal_log_level save private Stephen Hemminger
2018-04-24 23:55 ` Thomas Monjalon [this message]
2018-04-24 16:58 ` [dpdk-dev] [PATCH v2 4/5] log: add ability to match dynamic log based on shell pattern Stephen Hemminger
2018-04-25 0:02 ` Thomas Monjalon
2018-04-25 0:08 ` Thomas Monjalon
2018-04-24 16:58 ` [dpdk-dev] [PATCH v2 5/5] doc: update guides for current preferrred log level syntax Stephen Hemminger
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=1676287.Xq9lriP4j0@xps \
--to=thomas@monjalon.net \
--cc=dev@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).