[PATCH] kconfig: use va_end to match corresponding va_start

[PATCH] kconfig: use va_end to match corresponding va_start

[Colin King]

From: Colin Ian King <colin.king@canonical.com>

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>
---
 scripts/kconfig/confdata.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
index f88d90f..28df18d 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)
-- 
2.1.4

Re: [PATCH] kconfig: use va_end to match corresponding va_start

[Michal Marek]

On 2015-01-12 14:18, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> 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>

Applied to kbuild.git#kconfig, thanks.

Michal