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-Tag: firefly_0821_release~176^2~2276^2
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=b6a2ab2cd4739a9573ed41677e53171987b8da34;p=firefly-linux-kernel-4.4.55.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>
---

diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index f88d90f20228..28df18dd1147 100644
--- a/scripts/kconfig/confdata.c
+++ b/scripts/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)