Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix buffer overrun found by Coverity
Date: Tue, 09 Oct 2018 13:25:00 -0000	[thread overview]
Message-ID: <20181009132442.GA12668@blade.nx> (raw)
In-Reply-To: <87tvlwfiat.fsf@tromey.com>

Tom Tromey wrote:
> >>>>> "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,
> Gary> with the fission-dwp.exp board.  Assuming the dimensions thing
> Gary> above is correct, is this ok to commit?
> 
> Yes, thank you.

Cool, I've pushed it.  Thanks for the review :D

Cheers,
Gary


      reply	other threads:[~2018-10-09 13:25 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
2018-10-09 13:25       ` Gary Benson [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=20181009132442.GA12668@blade.nx \
    --to=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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