From: Colin Ian King <colin.king@canonical.com>
Date: Mon, 12 Jan 2015 13:18:26 +0000 (+0000)
Subject: kconfig: use va_end to match corresponding va_start
X-Git-Url: https://jxself.org/git/?a=commitdiff_plain;h=93bd65e141e01c6cee1418044bab688a76f19db7;p=carl9170fw.git

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 <colin.king@canonical.com>
Signed-off-by: Michal Marek <mmarek@suse.cz>
Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
---

diff --git a/config/confdata.c b/config/confdata.c
index 58ac13f..8028a9d 100644
--- a/config/confdata.c
+++ b/config/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)