From: Tom Tromey <tom@tromey.com>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add missing va_end found by Coverity
Date: Wed, 10 Oct 2018 13:01:00 -0000 [thread overview]
Message-ID: <87zhvmdkhp.fsf@tromey.com> (raw)
In-Reply-To: <1539163961-7279-1-git-send-email-gbenson@redhat.com> (Gary Benson's message of "Wed, 10 Oct 2018 10:32:41 +0100")
>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
Gary> gdb/ChangeLog:
Gary> * remote.c (remote_target::remote_send_printf): Add
Gary> missing va_end found by Coverity.
Thanks, this is ok. FWIW I would have been fine with the obvious rule
in this case.
Tom
next prev parent reply other threads:[~2018-10-10 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 9:32 Gary Benson
2018-10-10 13:01 ` Tom Tromey [this message]
2018-10-10 14:06 ` Gary Benson
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=87zhvmdkhp.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
/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