Skip to content

Commit

Permalink
kconfig: use va_end to match corresponding va_start
Browse files Browse the repository at this point in the history
Although on some systems va_end is a no-op, it is good practice
to use va_end, especially since the manual states:

"Each invocation of va_start() must be matched by a corresponding
invocation of va_end() in the same function."

Signed-off-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Michal Marek <mmarek@suse.cz>
  • Loading branch information
Colin Ian King authored and Michal Marek committed Jan 27, 2015
1 parent 09950bc commit b6a2ab2
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions scripts/kconfig/confdata.c
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,7 @@ static void conf_message(const char *fmt, ...)
va_start(ap, fmt);
if (conf_message_callback)
conf_message_callback(fmt, ap);
va_end(ap);
}

const char *conf_get_configname(void)
Expand Down

0 comments on commit b6a2ab2

Please sign in to comment.