From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 1/5] eal: make syslog facility table const
Date: Tue, 24 Apr 2018 09:58:04 -0700 [thread overview]
Message-ID: <20180424165808.23292-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20180424165808.23292-1-stephen@networkplumber.org>
The mapping fro facility name to value can be const.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/librte_eal/common/eal_common_options.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_eal/common/eal_common_options.c b/lib/librte_eal/common/eal_common_options.c
index 40c5b26f3c1d..0e6adcb9ddb5 100644
--- a/lib/librte_eal/common/eal_common_options.c
+++ b/lib/librte_eal/common/eal_common_options.c
@@ -881,7 +881,7 @@ static int
eal_parse_syslog(const char *facility, struct internal_config *conf)
{
int i;
- static struct {
+ static const struct {
const char *name;
int value;
} map[] = {
--
2.17.0
next prev parent reply other threads:[~2018-04-24 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:58 [PATCH v2 0/5] logging enhancements Stephen Hemminger
2018-04-24 16:58 ` Stephen Hemminger [this message]
2018-04-24 16:58 ` [PATCH v2 2/5] eal: allow symbolic log levels Stephen Hemminger
2018-04-24 16:58 ` [PATCH v2 3/5] eal: make eal_log_level save private Stephen Hemminger
2018-04-24 23:55 ` Thomas Monjalon
2018-04-24 16:58 ` [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 ` [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=20180424165808.23292-2-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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 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.