[PATCH v2 05/20] api-parse-options.txt: fix description of OPT_CMDMODE
- From
SZEDER Gábor <szeder.dev@gmail.com>
- Date
- Aug 19, 2022, 16:03 UTC
- Message-ID
- <20220819160411.1791200-6-szeder.dev@gmail.com>
- In-Reply-To
- <20220819160411.1791200-1-szeder.dev@gmail.com>
The description of the 'OPT_CMDMODE' macro states that "enum_val is set to int_var when ...", but it's the other way around, 'int_var' is set to 'enum_val'. Fix this.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com> --- Documentation/technical/api-parse-options.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/api-parse-options.txt b/Documentation/technical/api-parse-options.txt index acfd5dc1d8..5a04f3daec 100644 --- a/Documentation/technical/api-parse-options.txt +++ b/Documentation/technical/api-parse-options.txt @@ -236,7 +236,7 @@ There are some macros to easily define options: `OPT_CMDMODE(short, long, &int_var, description, enum_val)`:: Define an "operation mode" option, only one of which in the same group of "operating mode" options that share the same `int_var` - can be given by the user. `enum_val` is set to `int_var` when the + can be given by the user. `int_var` is set to `enum_val` when the option is used, but an error is reported if other "operating mode" option has already set its value to the same `int_var`.
-- 2.37.2.817.g36f84ce71d