From: Michal Marek <mmarek@suse.cz>
To: Colin King <colin.king@canonical.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: use va_end to match corresponding va_start
Date: Tue, 27 Jan 2015 16:59:40 +0100 [thread overview]
Message-ID: <54C7B5EC.1070706@suse.cz> (raw)
In-Reply-To: <1421068706-3689-1-git-send-email-colin.king@canonical.com>
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
prev parent reply other threads:[~2015-01-27 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 13:18 [PATCH] kconfig: use va_end to match corresponding va_start Colin King
2015-01-27 15:59 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C7B5EC.1070706@suse.cz \
--to=mmarek@suse.cz \
--cc=colin.king@canonical.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).