From cce666207f23bc57845e0533c1c6f761149e0425 Mon Sep 17 00:00:00 2001 From: Stefan Reinauer Date: Mon, 6 Apr 2015 01:14:21 +0200 Subject: kconfig: use va_end to match corresponding va_start 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 Signed-off-by: Michal Marek Change-Id: Ia08a57c37a6294e002cb6ce4c0a010c0d2edf973 Signed-off-by: Stefan Reinauer Reviewed-on: http://review.coreboot.org/9309 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel Reviewed-by: Marc Jones --- util/kconfig/confdata.c | 1 + 1 file changed, 1 insertion(+) (limited to 'util') diff --git a/util/kconfig/confdata.c b/util/kconfig/confdata.c index 149e27aec5..235debf614 100644 --- a/util/kconfig/confdata.c +++ b/util/kconfig/confdata.c @@ -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) -- cgit v1.2.3