From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Petri Latvala <petri.latvala@intel.com>
Subject: [igt-dev] [PATCH 2/4] lib/igt_core: 0 is a valid val for long options
Date: Wed, 5 Jun 2019 10:44:48 -0700 [thread overview]
Message-ID: <20190605174450.7235-2-lucas.demarchi@intel.com> (raw)
In-Reply-To: <20190605174450.7235-1-lucas.demarchi@intel.com>
This is usually used by long options when working with enum to set long
option values. So replace the strchr() with a memchr() to take that into
account.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
---
lib/igt_core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/lib/igt_core.c b/lib/igt_core.c
index 814f5c72..a0b7e581 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -680,6 +680,7 @@ static int common_init(int *argc, char **argv,
};
char *short_opts;
const char *std_short_opts = "h";
+ size_t std_short_opts_len = strlen(std_short_opts);
struct option *combined_opts;
int extra_opt_count;
int all_opt_count;
@@ -713,7 +714,7 @@ static int common_init(int *argc, char **argv,
/* check for conflicts with standard short options */
if (extra_long_opts[extra_opt_count].val != ':'
- && (conflicting_char = strchr(std_short_opts, extra_long_opts[extra_opt_count].val))) {
+ && (conflicting_char = memchr(std_short_opts, extra_long_opts[extra_opt_count].val, std_short_opts_len))) {
igt_critical("Conflicting long and short option 'val' representation between --%s and -%c\n",
extra_long_opts[extra_opt_count].name,
*conflicting_char);
@@ -727,7 +728,7 @@ static int common_init(int *argc, char **argv,
continue;
/* check for conflicts with standard short options */
- if (strchr(std_short_opts, extra_short_opts[i])) {
+ if (memchr(std_short_opts, extra_short_opts[i], std_short_opts_len)) {
igt_critical("Conflicting short option: -%c\n", std_short_opts[i]);
assert(0);
}
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-05 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 17:44 [igt-dev] [PATCH 1/4] lib/igt_core: reserve long options for individual tests Lucas De Marchi
2019-06-05 17:44 ` Lucas De Marchi [this message]
2019-06-05 17:44 ` [igt-dev] [PATCH 3/4] testdisplay: use first available option values Lucas De Marchi
2019-06-05 17:44 ` [igt-dev] [PATCH 4/4] lib/igt_core: add -h to usage Lucas De Marchi
2019-06-05 18:24 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [1/4] lib/igt_core: reserve long options for individual tests Patchwork
2019-06-06 9:20 ` [igt-dev] [PATCH 1/4] " Petri Latvala
2019-06-06 16:50 ` Lucas De Marchi
2019-06-07 11:53 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [1/4] " Patchwork
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=20190605174450.7235-2-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox