From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 4/5] log: add ability to match dynamic log based on shell pattern
Date: Wed, 25 Apr 2018 08:01:38 -0700 [thread overview]
Message-ID: <20180425080138.4dc94e2b@xeon-e3> (raw)
In-Reply-To: <762350822.UqGLKiTGi0@xps>
On Wed, 25 Apr 2018 11:38:21 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 25/04/2018 05:17, Stephen Hemminger:
> > --- a/lib/librte_eal/rte_eal_version.map
> > +++ b/lib/librte_eal/rte_eal_version.map
> > @@ -209,6 +209,13 @@ DPDK_18.02 {
> >
> > } DPDK_17.11;
> >
> > +DPDK_18.05 {
> > + global:
> > +
> > + rte_log_set_level_pattern;
> > +
> > +} DPDK_18_02;
>
> Must be DPDK_18.02 with a dot. Yes it is a trap.
>
>
Also the EXPERIMENTAL section needs to now depend
on 18.05
next prev parent reply other threads:[~2018-04-25 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 3:17 [PATCH v3 0/5] log level control enhancements Stephen Hemminger
2018-04-25 3:17 ` [PATCH v3 1/5] eal: make syslog facility table const Stephen Hemminger
2018-04-25 3:17 ` [PATCH v3 2/5] eal: allow symbolic log levels Stephen Hemminger
2018-04-25 3:17 ` [PATCH v3 3/5] eal: make eal_log_level save private Stephen Hemminger
2018-04-25 3:17 ` [PATCH v3 4/5] log: add ability to match dynamic log based on shell pattern Stephen Hemminger
2018-04-25 9:38 ` Thomas Monjalon
2018-04-25 15:01 ` Stephen Hemminger [this message]
2018-04-25 3:17 ` [PATCH v3 5/5] doc: update guides for current preferrred log level syntax Stephen Hemminger
2018-04-25 10:19 ` [PATCH v3 0/5] log level control enhancements 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=20180425080138.4dc94e2b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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.