From: Tom Tromey <tom@tromey.com>
To: Gary Benson <gbenson@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix buffer overrun found by Coverity
Date: Mon, 08 Oct 2018 17:41:00 -0000 [thread overview]
Message-ID: <87tvlwfiat.fsf@tromey.com> (raw)
In-Reply-To: <20181008163422.GA8415@blade.nx> (Gary Benson's message of "Mon, 8 Oct 2018 17:34:23 +0100")
>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:
Gary> I don't *think* it's necessary:
[...]
I agree, thanks for breaking it down for me.
Gary> Ok, so this one's built and regtested on RHEL 7.5 x86_64 now, with
Gary> the fission-dwp.exp board. Assuming the dimensions thing above is
Gary> correct, is this ok to commit?
Yes, thank you.
Tom
next prev parent reply other threads:[~2018-10-08 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 13:53 Gary Benson
2018-10-05 14:18 ` Tom Tromey
2018-10-08 16:34 ` Gary Benson
2018-10-08 17:41 ` Tom Tromey [this message]
2018-10-09 13:25 ` 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=87tvlwfiat.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