From: Tom Tromey <tromey@redhat.com>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Expand size of LEN parameter for invalidate_bp_value_on_memory_change
Date: Tue, 25 Sep 2012 20:48:00 -0000 [thread overview]
Message-ID: <87bogt25iz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120925193119.2cd0dd75@spoyarek> (Siddhesh Poyarekar's message of "Tue, 25 Sep 2012 19:31:19 +0530")
>>>>> "Siddhesh" == Siddhesh Poyarekar <siddhesh@redhat.com> writes:
Siddhesh> Attached patch expands the LEN parameter of
Siddhesh> invalidate_bp_value_on_memory_change to ssize_t to reflect the
Siddhesh> LEN that is actually sent by write_memory_with_notification.
Siddhesh> I have updated observer.texi accordingly so that the observer
Siddhesh> function signatures are correct (as well as the generated
Siddhesh> documentation). No regressions resulting from this change on
Siddhesh> x86_64. OK to commit?
Ok. Thanks for doing this.
Tom
prev parent reply other threads:[~2012-09-25 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 14:02 Siddhesh Poyarekar
2012-09-25 20:48 ` Tom Tromey [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=87bogt25iz.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=siddhesh@redhat.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