diff options
| author | Colin Ian King <colin.king@canonical.com> | 2015-01-12 13:18:26 +0000 |
|---|---|---|
| committer | Michal Marek <mmarek@suse.cz> | 2015-01-27 16:52:43 +0100 |
| commit | b6a2ab2cd4739a9573ed41677e53171987b8da34 (patch) | |
| tree | 4e6ac17be1d518a43e1da01d46e6e628b375c909 | |
| parent | 09950bc256e3628d275f90e016e6f5a039fbdcab (diff) | |
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>
| -rw-r--r-- | scripts/kconfig/confdata.c | 1 |
1 files changed, 1 insertions, 0 deletions
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) |